It is unfortunate that most server-packages don't seperate out their init scripts into separate packages:
- Contains the server binary, associated config files, and libraries.
- foo-run or foo-server
- Contains the init script(s).
Right now its a real pain to have to modify things like /etc/init.d/ssh to launch two daemons, running on two different ports, with two different configuration files.
Running multiple copies of SMTP daemons, databases, and similar things is basically more complex than it has to be, because our packages aren't setup for it.
If you maintain a daemon please do consider this, failing that honoring a flag such as "DISABLED=true" in /etc/default/foo would allow people to use their own /etc/init.d/foo.local initscript. (That's not perfect, but it is a step in the right direction.)
ObFilm: Little Miss Sunshine.
Tags: daemons, debian, mysql, ssh 12 comments
I have the same problem at work, also for things like
when you need the stuff installed but don’t want it
I think DISABLED in /etc/default/foo is a step into
the right direction, but I personally like flag files
more, since you can put them into place using a company
As of today, I use dpkg-statoverride on things like
smbd and nmbd, postgresql, apache2, and a simple script
with which the users of the PC can disable/enable them.