Dear Daniel (et al.), On 06 Sep 2002 10:52:07 -0700, Gordon Messmer <[EMAIL PROTECTED]> wrote:
> On Fri, 2002-09-06 at 09:39, daniel wrote: > > i understand how to put a command in the background by putting an > > '&' on the end, but it seems that this doesn't separate the > > command from that xterm. > ... > > # safe_mysqld & > ... > > then i exit the prompt and i /should/ get back machine (a)'s > > prompt but instead, i get a blank screen. > > <snip> > > In any case, running a program as 'command &' runs it as a job in > the background of your login shell. If you want it completely > detached, you have to run it from a different shell, like this: > ( command & ) > > It won't be associated any more, and you'll be able to log out > properly. I've found that you can also regain control from ssh, returning to the shell that ran it, by using the ~& escape sequence (only functional after a linefeed, or it would have just kicked _me_ off :). The escape sequence will background the ssh process, which seems to allow the shell to gracefully exit and orphan its own backgrounded process(es). Regards, Jonathan -- / Jonathan R. Johnson | "Every word of God is flawless." \ | Minnetonka Software, Inc. | -- Proverbs 30:5 | \ [EMAIL PROTECTED] | My own words only speak for me. / -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
