Date: Fri, 14 Nov 1997 15:33:42 -0500 From: Matthew Hunt <mph@pobox.com> To: dave@richcon.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: newsyslog and apache - logfiles changing their location... Message-ID: <19971114153342.08902@mph124.rh.psu.edu> In-Reply-To: <346C821C.1224@richcon.com>; from Dave Richards on Fri, Nov 14, 1997 at 09:53:48AM -0700 References: <346BDADD.1AFC@illumen.com> <346C821C.1224@richcon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 14, 1997 at 09:53:48AM -0700, Dave Richards wrote: > Ever since installation, we've seen strange behavior from newsyslog.. it > seems like the system cannot decide which logfile to write to, and has > switched back and forth two times thus far between * and *.0 The behavior is normal, and newsyslog is not responsible. When httpd starts up, it opens to log file you specify, and from that point on, it holds an open descriptor to that file. When newsyslog rotates the log, it changes the file's name, but httpd still has an open handle for the old log; the name of the file is not relevant. That's why, as man newsyslog states, newsyslog sends syslogd a HUP signal, instructing it to restart itself. httpd does not use syslogd, so it isn't informed that it should restart. Perhaps you could send httpd a HUP signal "by hand" after newsyslog runs. -- Matthew Hunt <mph@pobox.com> * Think locally, act globally. finger hunt@mph124.rh.psu.edu for PGP public key.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971114153342.08902>