If you want something that will not kill the process when you close the terminal you should look into screen. Screen is a virtual terminal that is not attached to a terminal so you can ssh to your machine from boxA and execute a command in screen, close the terminal, then ssh to your machine from boxB and "attach" to your screen session and you would be back to the prompt of the command you ran or your shell if the command finished. On Thu, Jan 29, 2009 at 3:24 AM, Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx> wrote: > > Hope this answers: > > the shell sends a SIGHUP to the program on shell termination, and if the > program does not handle/ignore it, it kills the program (nohup avoids this) > when the shell terminates (and the program set up to ignore the SIGHUP > signal), the shell waits (in vain) for the program to terminate (the shell > hangs instead of exiting) (nohup avoids this) > > -anuz > > > On Wed, Jan 28, 2009 at 11:13 PM, Vimal <j.vimal@xxxxxxxxx> wrote: >> >> 2009/1/28 nidhi mittal <nidhimittal19@xxxxxxxxx>: >> >> > >> > what i guess is may be evenHandler for windowClosing of terminal >> > explicitly >> > sends kill to all processes >> > which are children.. >> > >> >> A terminal emulator could do that (send a KILL to its children), but >> it doesn't. Wouldn't it be better for the terminal emulator to notify >> its children that it is being closed? SIGHUP is used for this. >> >> -- >> Vimal >> >> -- >> To unsubscribe from this list: send an email with >> "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx >> Please read the FAQ at http://kernelnewbies.org/FAQ >> > > -- -Stoyan -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
