Bug#702248: Non-optimal boot priority/dependency of service 'cups'
On Tue, Mar 05, 2013 at 06:28:54PM +0100, Didier 'OdyX' Raboud wrote:
> > This seems like a reasonable request, there are no dependency loops,
> > and the init system can cater for this need, so why should this not
> > just work by default? It's just a one line change to the init
> > script.
>
> The concern I have with adding this is that it makes the cups init script
> start after nslcd/slapd also in the default configuration, for unneeded
> reasons. Trying to cope with all possible configuration changes feels like
> opening the can of worms.
>
> So, I stand to my general "let's not try to cope with the world of change
> possibilities offered to the admin" but will apply this change to cups 1.6.1+
> in experimental. For users of other suites, /etc/init.d/cups is a
> configuration file, one can apply the attached patch directly.
Thanks for the patch!
Coping with all possible configuration possibilities is indeed a
can of worms, but in this case the ordering is completely
unambiguous, and this type of dependency information is very
useful--any time an end user needs to tweak this stuff indicates
a failure on our part to not make things Just Work. We don't
know when an admin might start making use of this directive,
so having it work 100% of the time is a good thing.
The only time end users need to manually tweak this stuff is
where there are multiple ways to order things e.g. encrypted
root on lvm on raid etc. where we can't know the correct
order in advance for all possible systems. Even then, we
do the right thing for the typical common cases.
Thanks again,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
Reply to: