On Wed, Oct 13, 1999 at 09:33:14AM +0100, Tim Phipps wrote:
> Jason Kibblewhite wrote:
> > Well hardly being the expert here but all the window managers that I've
> > tried also do this. Those including Window Maker, AfterStep, E, TWM,
> > Olvwm and a few others hardly worth mentioning. I just use the start from
> > xterm and exit the xterm which seems to work just fine for me.
>
> It probably depends on your shell and how it behaves when recieving
> signals, it might depend on you terminal emulator but I expect they all
> behave the same, it won't depend on your window manager.
>
> When your terminal emulator is killed by the window manager it will send
> a -HUP signal to the shell it is running. Most shells react to -HUP by
> killing all their children (with -HUP so it can propogate) and exiting.
> Killing the shell -KILL will just kill it with no chance of it being
> able to interfere with its children. Exiting a shell may or may not kill
> its children, it depends on the shell and is probably configurable.
>
> You can prevent -HUP from propogating to children with the nohup command
> though it tends to create nohup.out files.
With zsh it's very easy to do this without an output file and
without 'nohup':
# my_program &!
^^
This makes the created process a child of init. Thus the shell can't
kill it when it exits. You can do something similar with ksh compatible
syntax:
# (my_program &)
Bye
Dominik ^_^
--
Dominik Vogt, Hewlett-Packard GmbH, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/14-4596, fax: 07031/14-3883, dominik_vogt_at_hp.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Oct 13 1999 - 06:41:51 BST