Dmitriy Matrosov wrote: > 2011/11/24 Arno Schuring <aelschur...@hotmail.com>: >> lrhorer (lrho...@satx.rr.com on 2011-11-24 03:38 -0600): >>> OK, so here's the deal. I compiled and installed ncid on one of my >>> Debian servers Everything seems to be working just fine. There's >>> one small item, though. When I took the init scripts and ran >>> update-rc.d, it gave me a warning saying "stop runlevel arguments (0 >>> 1 6) do not match LSB Default-Stop values (S 0 1 6)". When I looked >>> at the scripts, they have the line >>> >>> # Default-Stop: S 0 1 6 >>> >> [..] >>> First of all, why did the routine put up that warning and fail to >>> create the links? >> insserv doesn't create the links unless explicitly asked to do so. By >> default (as it's called from dpkg), it only determines start/stop >> ordering. >> >> I'm not sure how those links are populated initially. It could be >> that the package provides them, and is missing that one link. >> >> To restore the defaults, run: >> # insserv -vd ncid >> >> <..> >> >> Regards, >> Arno > > It seems, that 'insserv -d' also reorders other init scripts (though i > don't understand why)
Um, because it is supposed to? I mean, the whole point of dependency based booting is to make sure the proper services are all available when they need to be, and the mechanism of that is the ordering of the scripts. Whenever one script changes, it may affect other scripts. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/75ednr1cyl8chvptnz2dnuvz5rsdn...@giganews.com
