kill xterm kills app!
Jay Daniels
drs at pointyhats.com
Thu Apr 29 03:57:29 UTC 2004
On Wed, Apr 28, 2004 at 10:24:35PM -0500, Paul D. Brown wrote:
> On Wed, 2004-04-28 at 10:18, Jay Daniels wrote:
> > If I open a terminal and run a program in the background using the "&"
> > when I close the terminal the program gets killed.
> >
> > xclock &
> > x out of terminal kills xclock!
> >
> > How do I prevent this?
> >
> >
> > jay
> >
>
> If you start it with the ampersand and later want to close the xterm but
> keep the other app (xclock) going, you can use 'disown' to do the same
> thing that 'nohup' does when starting it as mentioned in earlier posts.
> For example:
>
> $ xclock &
> $ disown xclock
>
> Paul
Why does xclock become a child of the xterm process if you use the
ampersand and run it in the background?
I hope the console doesn't work this way. If you start a server from
the console as root, it doesn't die when you logout does it?
jay
More information about the fedora-list
mailing list