[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#647075: marked as done (please support RUN in /etc/default/apache2)



Your message dated Sat, 3 Dec 2011 18:03:23 +0100
with message-id <201112031803.23791.sf@sfritsch.de>
and subject line Re: Bug#647075: please support RUN in /etc/default/apache2
has caused the Debian Bug report #647075,
regarding please support RUN in /etc/default/apache2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
647075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647075
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Version: 2.2.21-2
Severity: wishlist

Would it be possible to support an option "RUN" or
"START_DAEMON" in /etc/default/apache2, similar to
other packages?

Apache2 is supposed to be started by other means on
my systems. Creating /etc/insserv/overrides/apache2
appears a little bit too complex just to make sure
that it is not started at boot time.

Setting the default to "true" would be fine with me.


Many thanx

Harri



--- End Message ---
--- Begin Message ---
We had a no start option in /etc/default/apache2 in the past and it 
caused quite a lot of pain.

On Wednesday 02 November 2011, Harald Dunkel wrote:
> insserv -r is no option, because on the next update the default run
> level symlinks are reinstalled again. Thats even worse than
> creating a private overrides file for insserv.

update-rc.d nowadays has enable/disable commands for end-users, which 
do the right thing in order not to get lost on updates. Therefore we 
are not going to reinvent the wheel in the apache package.

> Not to mention that
> insserv nags about some "non-default" run level symlinks all the
> time.

If that is bothering you, please file a bug on insserv.



--- End Message ---

Reply to: