Thanks for the help. The ampersand doesn't always work but nohup definitely does. Cleary_Mike@emc.com wrote:
Use nohup - nohup runs a command such that the command continues running after you log out.
# nohup COMMAND <arguments>
Type "info nohup" for more explicit information Hope that's what you need..
Mike ----------------------------------------------------- Cleary_Mike@emc.com ----------------------------------------------------- Yesterday it worked. Today it is not working. Windows is like that.
-----Original Message----- From: expatriate [mailto:lbox@nellgc.plus.com] Sent: Tuesday, July 15, 2003 8:17 AM To: suse-linux-e@suse.com Subject: [SLE] background process and controlling terminal
Sorry for this newbie question. I know I could eventually dig this up but why not (ab)use the list? Coming from a Solaris background, I'm quite used to opening terminals, launching jobs in the background and opening other terminals etc etc and then killing windows at will as the desktops get cluttered. However, in Linux, if I launch some applications in the background and then kill their terminal window, the applications terminate as well. Is this Linux's way to avoid zombies or is there some other way to launch an app and completely sever its ties to the window process that launched it? TIA & cheers