On Mon, Jul 06, 2009 at 12:56:10AM +0200, Enrico Zini wrote:
> What seems needed here is to have the supervisor to detect that the
> child has been killed with signal 15, and in that case just quit.
>
> It should be easy enough to do, and quite ok because if I kill, for
> example, matchbox, nodm/
On Sat, Jun 06, 2009 at 10:51:12PM +0200, M. Dietrich wrote:
> > Did you find a way to reliably reproduce it all the time?
> yes, i can just do a
> kill
> and it restarts. i may be a wrong reaction on signal 15.
I've tried. There are two nodm processes running: one is the X session
and on
On Fri, Jun 05, 2009 at 12:40:06PM +0200, Enrico Zini wrote:
> On Thu, Jun 04, 2009 at 06:22:38PM +0200, M. Dietrich wrote:
>
> > if using
> > /etc/init.d/nodm stop
> > the session just restarts. this should entirely end the running nodm.
>
> I have occasionally noticed this behaviour, but I
On Thu, Jun 04, 2009 at 06:22:38PM +0200, M. Dietrich wrote:
> if using
> /etc/init.d/nodm stop
> the session just restarts. this should entirely end the running nodm.
I have occasionally noticed this behaviour, but I have not been able to
reproduce it to be able to debug it.
Did you find
Package: nodm
Version: 0.4-1
Severity: normal
if using
/etc/init.d/nodm stop
the session just restarts. this should entirely end the running nodm.
-- System Information:
Debian Release: squeeze/sid
Architecture: i386 (i686)
Kernel: Linux 2.6.29-2-686-bigmem (SMP w/2 CPU cores)
Locale:
5 matches
Mail list logo
