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 <pid> > 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 one is the supervisor. Killing the supervisor terminates nodm properly, while killing the X session causes the supervisor to restart it. 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/xsession won't exit as killed with signal 15 and so the nodm/supervisor will properly restart it as it should. I'm doing some triaging of the open nodm bugs to organise my work on it in the next days. Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
