Re: Bug#3059: No more logs since cron.weekly rotation

[Steve Greenland <stevegr@starbase.neosoft.com>]

Dirk.Eddelbuettel@qed.econ.queensu.ca wrote:
> 
> As a follow-up, now with sysklogd-1.3-3 working (after some stress, see
> bug#3060), I still have the httpd log untouched since cron.weekly ran.  (And
> yes, I fired up some www browsers so there should be some activity.)
> 
> -rw-r--r--   1 root     adm             0 May 19 06:47 httpd.log
> -rw-r--r--   1 root     adm             0 May 19 06:47 httpd.log.0
> -rw-r--r--   1 root     adm             0 May 19 06:47 httpd-error.log
> -rw-r--r--   1 root     adm             0 May 19 06:47 httpd-error.log.0
> 
> Is this also a problem with sysklogd or does the httpd it's own logging? (I
> use cern-httpd-3.0-4).

cern-httpd does its own logging. I think what you're seeing there is the
problem where the daemon doesn't re-open the files, thus it's still 
happily logging to the log file it started with, now long since rotated
out of existence by savelog, but still taking up space on your disk,
and totally useless since you can't access it (unless you're a kernel
hacking god, which I'm not...). 

Anyway, it's fixed in cern-httpd-3.0-5, which I (finally!) uploaded a
couple of weeks ago. Alternatively, you can just add this line
to /etc/cron.weekly/cern-httpd:

/usr/sbin/httpd -restart

(which is actually /usr/sbin/cern-httpd in the -5 release).

SteveG

-- 
The Mole - I think, therefore I scream 

			   "I left the tri-corder on
			    `The Wild, Chunky,
			     Spunky Planet of
			     Mary Lou Retton
			     Clones.'"
						    "Spock, you are SUCH a
						     putz."
[BLOOM COUNTY]