On Fri, May 19, 2006 at 03:23:19PM +0200, Sander van Dijk wrote: > On 5/19/06, Anselm R. Garbe <[EMAIL PROTECTED]> wrote: > >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. > > > Hi Anselm, > > Reading this, I must confess that I have been a bit too trigger-happy > when 'removing unnecessary wmiisetsid calls'. I removed the wmiisetsid > before the xterm keybinding in wmiirc too :-(. > I thought that using it for the proglist was enough, somehow I > overlooked that problematic apps might be started from a M-Enter > started xterm as well... > I suggest you readd the wmiisetsid to the xterm binding and quickly > rerelease wmii-3. > Sorry about this...
No, xterm catches SIGHUP, thus it is not exit. Regards, -- Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361 _______________________________________________ [email protected] mailing list http://wmii.de/cgi-bin/mailman/listinfo/wmii
