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

Bug#414193: marked as done (apache2-common: searching ALL files in /etc/apache2 for PidFile)



Your message dated Tue, 6 May 2008 00:21:57 +0200
with message-id <200805060021.57595.sf@sfritsch.de>
and subject line #414193 apache2-common: searching ALL files in /etc/apache2 for PidFile
has caused the Debian Bug report #414193,
regarding apache2-common: searching ALL files in /etc/apache2 for PidFile
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.)


-- 
414193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414193
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apache2-common
Severity: important


In /etc/init.d/apache2, when a reload is requested (as is the case from
the package manager during upgrades )  ALL files in /etc/apache2  are
greped for a line begining with "^PidFile".  If there was some file with
a name like config.old that had a line that began with PidFile, it would
be used.

More importantly, some servers have lots of BIG log file in
/etc/apache2/logs, left over from an earlier standard, and all of those
log files are searched entirely for lines begining with PidFile.

This takes A VERY LONG TIME, and caused great anxiety to the poor
sysadmin running a live server and waiting to breath again when the
server has successfully restarted.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)


--- End Message ---
--- Begin Message ---
Version: 2.2.8-1

This has been fixed in 2.2.8-1


--- End Message ---

Reply to: