38787 – /etc/init.d/apache2 must define default values

Bug 38787 - /etc/init.d/apache2 must define default values

Summary: /etc/init.d/apache2 must define default values

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Server (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Gentoo Web Application Packages Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-01-20 00:41 UTC by Bernd Wurst
Modified:	2004-01-20 01:55 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Bernd Wurst 2004-01-20 00:41:14 UTC

I upgraded apache2 to newest Version and denied updating of /etc/conf.d/apache2 because I did not want to loose the configured Apache-Opts.

After deleting the new default config file, I saw that apache can no longer be started via init-Script!! The init-Script fully depends on $PIDFILE to be set in conf.d and does not assume any default. This is *not* good!

Comment 1 Robin Johnson archtester

2004-01-20 01:50:48 UTC

fixed in CVS.
if you elected to update the init.d file you should always update the conf.d file as well, as the two are heavily linked.

Comment 2 Bernd Wurst 2004-01-20 01:55:32 UTC

Thanks for fixing, but I disagree with your opinion.

The init.d-Script is the technical init-process and should always be updated, because it reflects changes in (e.g. apache's) startup procedure.
The conf.d is for my own settings. If I don't want to change anything, I don't want to update. 
If I always have to take care of changes in both of them, why are there two if it? I see that there are new variables defined in conf.d but I don't mind where the PIDfile is, so I think I don't have to update my config, the default will do it.