On Fri 2016-08-05 15:03:29 -0400, Peter Colberg wrote: > On Fri, Aug 05, 2016 at 01:51:07PM -0400, Daniel Kahn Gillmor wrote: >> I don't think there's any need to add no-autostart in this case. in >> particular, the daemon will already be running, so any consideration of >> autostart will just detect and make use of the already-running daemon. > > This is precaution to detect when the daemons are *not* running, e.g., > if the systemd services have not been started due to misconfiguration.
if the systemd service can't start due to misconfiguration, then it
seems likely that the autostarted daemons would fail in the same way,
which would result in the same situation. But at least the tools would
try to start them if they see that they're not available. and autostart
probably needs to be present for non-systemd systems anyway, right?
My long-term goal is to have these things Just Work without *any*
explicit user intervention.
That is, i want: "If the package is installed, it should work for you."
and not: "oh, if you want things to actually work, just fiddle these
bits in that file over here." Debian should provide a high level of
simple and easy system integration where it can.
by adding no-autostart, we'd be saying "in case your systemd service
can't start the agent, then we don't want to even try to start up the
agent." but i think it would be better to actually try, since it's
likely that this is what the user wants to do.
--dkg
signature.asc
Description: PGP signature
