Hello Friends If '&' makes bash push something to background, it must be a child process of 'bash'. And so, when the user logs out, the parent bash dies, and hence this child ps gets killed.
Exactly what is happening when i start 'emacs &', and then hit 'Ctrl-d', first bash warns me that there are unfinished jobs, and then with a second 'Ctrl-d' logs me out. I 'Ctrl-F2' to the second virtual terminal, where root is logged in, and see that the emacs process in not anymore there in the 'ps aux' list. But, a queer thing happened with lame. While revamping a bad quality mp3 file with 'lame -q 0 -V 0', which obviously takes an infinitely long time, i started it with '&', and though it was throwing the histograms to my standard out, after doing some works, i logged off, with 'Ctrl-d', expecting the process to end there. and still the process was running. Process list was showing in other VT-s, and 'top' was showing the very big demand of resource by lame. This stopped when lame finished its job. And the only way out from this was to kill the lame process specifically from some other VT or after re-logging-in. This is predictable when i start the command with 'lame ... & nohup', and then, as predictable, the 'nohup.out' file is carrying all the histograms, when the process is going on. That is what 'nohup' is meant for. To go on with the jobs even when i log out. But with 'lame ... &', why this will happen? What is the thing here that i am missing? This is my experience that whenever bash seems illogical, somewhere it is some of my stupid mistakes working. What is that here? dipankar das -- To unsubscribe, send mail to [EMAIL PROTECTED] with the body "unsubscribe ilug-cal" and an empty subject line. FAQ: http://www.ilug-cal.org/node.php?id=3
