<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Mon, Apr 27, 2015, at 13:19, Borut Mrak wrote:<br></div>
<blockquote type="cite"><div><span style="font-family:menlo,consolas,"courier new",monospace" class="font">I'm working on update-rc.d to add this feature (got bitten by
this using saltstack service states on Jessie w/ systemd).</span><br></div>
<div> </div>
<div><span style="font-family:menlo,consolas,"courier new",monospace" class="font">
I simplified Michael's idea a little bit (I think).</span><br></div>
<div> </div>
<div><span style="font-family:menlo,consolas,"courier new",monospace" class="font">
Instead of checking if links correspond to Default-Start +
Default-Stop, i'm just checking if there are all the Default-Start
links available.</span><br></div>
<div> </div>
<div><span style="font-family:menlo,consolas,"courier new",monospace" class="font">
For is-disabled I'm only checking that there are no S links
present in Default-Start runlevels.</span><br></div>
<div> </div>
<div><span style="font-family:menlo,consolas,"courier new",monospace" class="font">
IMO, no links == disabled (I know they get recreated on upgrades,
but that is out of scope for this feature).</span><br></div>
<div> </div>
</blockquote><div> </div>
<div>This is a problem. The sysv-rc model requires you to
actually look at the symlinks to know whether a service is enabled/disabled,
the LSB headers are more like the metadata which stores "default/upstream
recommended/initially-configured state", as well as dependency information.<br></div>
<div> </div>
<div>I.e. the LSB headers do NOT matter at all for sysv-rc (the thing that actually runs the initscripts): they are not in any way related to how the system will behave. They're ancillary metadata which is used by update-rc.d (plus startpar for dependency handling) when setting up the symlink farm.<br></div>
<div> </div>
<div>Admins are expected, and *do* interact with sysv-rc through the symlink farm without editing the LSB headers.<br></div>
<div> </div>
<div>Can
you change this to actually look for the presence of S/K symlinks?
Beware the way S/K symlinks are used on runlevels 0 and 6, as it could
cause some confusion (I hope there is no need for special casing, but
this needs to be carefully considered).<br></div>
<div id="sig1082268"><div class="signature"> </div>
<div class="signature">--<br></div>
<div class="signature">"One disk to rule them all, One disk to find them. One disk to bring<br></div>
<div class="signature">them all and in the darkness grind them. In the Land of Redmond<br></div>
<div class="signature">where the shadows lie." -- The Silicon Valley Tarot<br></div>
<div class="signature">Henrique de Moraes Holschuh <hmh@debian.org><br></div>
</div>
<div> </div>
</body>
</html>