On Tuesday, March 08, 2011 12:22:13 PM Matthias Metzger wrote: > Hi, > > just one question. > http://robbyx.net/blog/?p=190 says: "Inserting a link to nvdown that > will not be needed by any other daemon: update-rc.d nvdown defaults 98 02". > But why? Is there any handicap using just "update-rc.d nvdown defaults"? > What problem could raise? > > Thank you > > Matthias > > _______________________________________________ > Mailing list: https://launchpad.net/~hybrid-graphics-linux > Post to : [email protected] > Unsubscribe : https://launchpad.net/~hybrid-graphics-linux > More help : https://help.launchpad.net/ListHelp
Hi Matthias, If defaults is used then update-rc.d will make links to start the service in runlevels 2345 and to stop the service in runlevels 016. By default all the links will have sequence number 20, but this should be overridden if there are dependencies. For example if daemon B depends on A, then A must be started before B and B must be killed before A. You accomplish this by supplying two NN arguments. In general, core daemons should start early and be killed late, whilst applications can start late and be killed early. In this case nvdown is not used or depending on other daemons, and it's just a helper script, so it's started late and stopped early. You could go with just "defaults" if you wish. Regards, -- Olivier Robert _______________________________________________ Mailing list: https://launchpad.net/~hybrid-graphics-linux Post to : [email protected] Unsubscribe : https://launchpad.net/~hybrid-graphics-linux More help : https://help.launchpad.net/ListHelp
