On Mon, Sep 21, 2009 at 11:09:50PM -0300, Henrique de Moraes Holschuh wrote: > Well, I have found the bug. The way it is written, invoke-rc.d would > never get exit status 1 from runlevel. This bug has been in there since > invoke-rc.d was deployed, and I won't pretend I recall why I screwed > that up more than 8 years ago. > > Now, fixing it is not difficult. However, it is a codepath that was > NEVER reached before, so a lot of stuff out there might object to > invoke-rc.d exiting with status 102 in every chroot that /sbin/runlevel > doesn't like. > > Maybe it would make more sense to proceed with an unknow runlevel, > instead. Invoke-rc.d can deal with it, it will just ignore any symlinks > (it won't even test them), call policy-rc.d without a runlevel (which is > supported by the interface) if one exists, and behave as it would for a > initscript missing the symlinks.
This will change the behaviour by not starting services in the chroot. This is atleast a default I would like to see. But I wonder if we need to have a way of allowing services to be started in a chroot or not. I've currently only ran a service from a chroot manually. Kurt _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
