Your message dated Wed, 21 Dec 2016 17:39:24 -0300 with message-id <CAAfdZj8_14WXp0x89GwDKfGGHyF7AzOWA-nRD59T_=t+6or...@mail.gmail.com> and subject line Re: invoke-rc.d was ignoring the exit status of runlevel has caused the Debian Bug report #361717, regarding invoke-rc.d: always restarts services in a chroot, runlevel unknown to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 361717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: sysv-rc Version: 2.86.ds1-61 Scenario: I want to update Debian within a chroot environment. To make sure that no runlevel scripts are started I install a policy-rc.d file in /usr/sbin saying #!/bin/sh exit 101 Problem: During the update I get several warnings saying invoke-rc.d: ---------------------------------------------------- invoke-rc.d: WARNING: invoke-rc.d called during shutdown sequence invoke-rc.d: enabling safe mode: initscript policy layer disabled invoke-rc.d: ---------------------------------------------------- (e.g. for cron). Of course there is no shutdown sequence going on. /var/run/utmp and others (maybe some forgoten *.pid files, or whatever) in the chroot are in an undefined state, so the init scripts should not be run. Thats the reason _why_ I have put policy-rc.d into place. And surely I do not want another cron daemon running in a foreign environment keeping the chroot busy. I think that policy-rc.d should get a higher priority here. Regards Harri
--- End Message ---
--- Begin Message ---Version: 1.32 On Mon, 21 Sep 2009 23:09:50 -0300 Henrique de Moraes Holschuh <h...@debian.org> 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. This was fixed by Martin in version 1.32. Marking as fixed. Saludos
--- End Message ---
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
