Re: [wmii] killall telnet kills wmii

On Fri, May 19, 2006 at 02:13:39PM +0200, Konstantin Kletschke wrote:
> I start wmii by "exec wmii" in ~/.xinitrc.
>
> wmiiwm - 20060504-rc2-slavutych, (C)opyright MMIV-MMVI Anselm R. Garbe
>
> Very often "killall telnet" in an xterm closes X entirely:
>
>
> waiting for X server to shut down xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> ..xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> .xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
> .FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing.
>
>
> --> ?
>
> Thats not funny! ;)

This should be fixed in wmii-3, because we introduced the tiny
wmiisetsid tool which allows to execute processes in their own
process group (telnet and those apps from plan9port send SIGHUP
to their process group, which would exit wmii in such a case).

Just update to the release and you will be happy.

PS: The wmiisetsid tool has been introduced, because not every
platform contains a command line tool for this, e.g. Linux does
have setsid(1), but BSDs usually only have the syscall, but no
command line tool.

Regards,

-- 
 Anselm R. Garbe  ><><  www.ebrag.de  ><><  GPG key: 0D73F361