Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
On Thu, Nov 12, 2009 at 09:03:59AM -0600, Raphael Geissert wrote: > Michael Hanke wrote: > [...] > > > > Can anyone please point me to the problem and its solution? > > > > When making changes to the runlevels either via update-rc.d or the lsb > header, the init script needs to be removed first (via update-rc.d, as > simply removing the symlink won't work in the case of file-rc). Ah! Thanks a lot, that explains it. > In other words: you need to check if the user is upgrading from an affected > version (probably anything lt the new version) and then do an update-rc.d > remove. All that before the #DEBHELPER# mark so that the rest is done for > you. > > And like Rogéiro Brito said, remove the S runlevel. First of all, S is only > used by some special cases where the script only needs to be run once, > second, syslog daemons are only available from post-rcS (which at some > point would render your package uninstallable because of unmet init script > dependencies). Well, the respective package is a firewall. I'd say it should run once in S pretty much right after networking becomes available. It may even not be necessary to run it again when switching to a runlevel other then 0 1 6, correct? So instead of removing S I should remove 2 3 4 5, I guess. Additionally, as you mentioned syslog is not available at that early stage. The question is now whether I should sacrifice the startup log-message for the sake of establishing the firewall as early as possible -- or not? Oppinions very much appreciated! Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
Michael Hanke wrote: [...] > > Can anyone please point me to the problem and its solution? > When making changes to the runlevels either via update-rc.d or the lsb header, the init script needs to be removed first (via update-rc.d, as simply removing the symlink won't work in the case of file-rc). In other words: you need to check if the user is upgrading from an affected version (probably anything lt the new version) and then do an update-rc.d remove. All that before the #DEBHELPER# mark so that the rest is done for you. And like Rogéiro Brito said, remove the S runlevel. First of all, S is only used by some special cases where the script only needs to be run once, second, syslog daemons are only available from post-rcS (which at some point would render your package uninstallable because of unmet init script dependencies). Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
On Nov 11 2009, Michael Hanke wrote:
> # Default-Start: S 2 3 4 5
Remove the S state.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
On Wed, Nov 11, 2009 at 04:44:13PM +0200, Peter Pentchev wrote: > On Wed, Nov 11, 2009 at 03:35:40PM +0100, Didier 'OdyX' Raboud wrote: > > Michael Hanke wrote: > > > > > Hi, > > > > > > Can anyone please point me to the problem and its solution? > > > > Hi Michael, > > > > without pre-judging your problem and its solutions, this is the wrong list > > for this type of problems. > > > > debian-mentors mailing list > > Helping newbie developers > > Newbie Debian developers can seek help with packaging and other > > developer- > > related issues here. > > This list is not meant for users' questions, but for new maintainers'! > > > > Please re-post your question to debian-u...@lists.debian.org > > Well, that would have been fine, except that Michael Hanke is actually > the maintainer of the arno-iptables-firewall package, and he may be > asking this question from a "what can I do to make my package work" > point of view :) That is correct -- maybe I should have mentioned that. I won't to actually prevent people having to post to -users, because they are concerned by that warning message. Thanks in advance, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
Peter Pentchev wrote: > On Wed, Nov 11, 2009 at 03:35:40PM +0100, Didier 'OdyX' Raboud wrote: >> Hi Michael, >> >> without pre-judging your problem and its solutions, this is the wrong >> list for this type of problems. > > Well, that would have been fine, except that Michael Hanke is actually > the maintainer of the arno-iptables-firewall package, and he may be > asking this question from a "what can I do to make my package work" > point of view :) > > G'luck, > Peter D'oh ! Here are my very sorry public apologies. I am really sorry for that "I am too tired to see with my eyes" error. … ++, OdyX -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
On Wed, Nov 11, 2009 at 03:35:40PM +0100, Didier 'OdyX' Raboud wrote: > Michael Hanke wrote: > > > Hi, > > > > Can anyone please point me to the problem and its solution? > > Hi Michael, > > without pre-judging your problem and its solutions, this is the wrong list > for this type of problems. > > debian-mentors mailing list > Helping newbie developers > Newbie Debian developers can seek help with packaging and other > developer- > related issues here. > This list is not meant for users' questions, but for new maintainers'! > > Please re-post your question to debian-u...@lists.debian.org Well, that would have been fine, except that Michael Hanke is actually the maintainer of the arno-iptables-firewall package, and he may be asking this question from a "what can I do to make my package work" point of view :) G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 If this sentence were in Chinese, it would say something else. pgp5Q5EFoCS5C.pgp Description: PGP signature
Re: insserv: warning: current stop runlevel(s) ... overwrites defaults
Michael Hanke wrote: > Hi, > > Can anyone please point me to the problem and its solution? Hi Michael, without pre-judging your problem and its solutions, this is the wrong list for this type of problems. debian-mentors mailing list Helping newbie developers Newbie Debian developers can seek help with packaging and other developer- related issues here. This list is not meant for users' questions, but for new maintainers'! Please re-post your question to debian-u...@lists.debian.org > Thanks, > > Michael Best regards, OdyX -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
insserv: warning: current stop runlevel(s) ... overwrites defaults
Hi, I recently switch to dependency-based boot order. While updating one of my packages I noticed an inconsistency of init script LSB header and update-rc.d call. I have trouble figuring out what would be the appropriate fix. The LSB header looks like this: ### BEGIN INIT INFO # Provides: arno-iptables-firewall # Required-Start:$syslog $local_fs $network # Required-Stop: $syslog $local_fs $network # Default-Start: S 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Setup iptables firewall configuration ### END INIT INFO I am trying to find the matching update-rc.d call, but no luck so far: : update-rc.d arno-iptables-firewall start 41 2 3 4 5 S . stop 34 0 1 6 . update-rc.d: using dependency based boot sequencing insserv: warning: current start runlevel(s) (S) of script `arno-iptables-firewall' overwrites defaults (2 3 4 5 S). insserv: warning: current stop runlevel(s) (empty) of script `arno-iptables-firewall' overwrites defaults (0 1 6). The above call should match precisely what I want -- it looks like the arguments of the call are not considered as a whole. Going with the defaults also doesn't help: : update-rc.d arno-iptables-firewall defaults 41 34 update-rc.d: using dependency based boot sequencing update-rc.d: warning: arno-iptables-firewall start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (S 2 3 4 5) insserv: warning: current start runlevel(s) (S) of script `arno-iptables-firewall' overwrites defaults (2 3 4 5 S). insserv: warning: current stop runlevel(s) (empty) of script `arno-iptables-firewall' overwrites defaults (0 1 6). Can anyone please point me to the problem and its solution? Thanks, Michael -- GPG key: 1024D/3144BE0F Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
