You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run a shell through my BBS for remote management and I simply start it with runfifo newshell window *. This works well enough for most things but if I do a ping or something similiar which expects a Ctrl-c (SIGBREAKB_CTRL_C) to exit, this gets lost and I have no way to stop the program except for logging in again, start another program and stop it with break.
It would be great if there was some way to let Ctrl-C signal get passed through the command running through runfifo.
The text was updated successfully, but these errors were encountered:
I run a shell through my BBS for remote management and I simply start it with runfifo newshell window *. This works well enough for most things but if I do a ping or something similiar which expects a Ctrl-c (SIGBREAKB_CTRL_C) to exit, this gets lost and I have no way to stop the program except for logging in again, start another program and stop it with break.
It would be great if there was some way to let Ctrl-C signal get passed through the command running through runfifo.
The text was updated successfully, but these errors were encountered: