On Wednesday 28 April 2004 18: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?
How did you get this? I could not reproduce it - my xclock stays.
You can however use:
(xclock < /dev/null > /dev/null 2>&1 &)&
This way xclock reads and writes to /dev/null (can't die due to
terminal IO) and will not be killed when exiting current shell 'cause
it will not be aware of xclock's existance (xclock will be init's child).
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
