Ksh also does not terminate its children by default when exiting, and nohup is needed. However when you terminate bash by typing "exit" or control-D, it doesn't send a TERM to its children. What actually happens when you click the red "close" button is that the system sends a TERM (exit) signal to the shell - and when bash receives a TERM signal, it sends a TERM to all of its children before it exits itself. So the simple solution might be to close your shell by typing "exit" or control-D instead of clicking the close button. However, from just testing now, it appears that if you click the red "close" button, Terminal itself terminates bash AND its children for you. I think it's default behaviour though - pretty sure. That is, it does not terminate its children on my system, but I've long forgotten if that was something I configured myself, or the default behavior.
However, the bottom line is that you can control whether a shell's subprocesses (bash = your shell) are terminated, when the shell is terminated.īy default, I don't think bash itself terminates its backgrounded children, when you exit bash (by typing control-D or exit).
OS X MIDI FILE PLAYER FULL
This is a little complicated - the full details are far too involved to go into right here. It'll take a little bit of learning to get used to it (the man page is VERY big), but I absolutely swear by screen. The only thing screen doesn't do is survive a reboot (go figure). It's all still there to reconnect to when you re-open Terminal and reconnect to it. If you're running screen, and terminal crashes, nothing happens to screen. Be forewarned this is a VERY extreme example. It serves an excellent second purpose that if you're doing something (say, ssh'ed into a remote server) and your connection goes away, everything you were doing inside screen continues to run, or everything you have done remains there in context until you reconnect to the server and resume screen. Screen is a "terminal multiplexer", it allows you to turn one terminal into many all self contained. Nohup will continue command execution until completion (or failure, either way a program exit), and then it'll go away.
OS X MIDI FILE PLAYER HOW TO
Or you can learn how to use the 'screen' command. One is that you can use the 'nohup' command to continue command execution even if the shell goes away. You have two options, and both may be a bit more involved than you want to be. (Applications don't run without a controller of some manner.) Using & puts it in the background of the shell, but if you kill the shell, you kill that application as well. Don't worry that you're doing something wrong.
0 kommentar(er)
