Date: Thu, 15 Apr 2010 11:31:21 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Log rotation / newsyslog / apache not reloaded Message-ID: <4BC6EAF9.7020002@infracaninophile.co.uk> In-Reply-To: <4BC6E58E.12367.3389FE7@z.szalbot.lcwords.com> References: <4BC6B286.16120.2714AA3@z.szalbot.lcwords.com> <4BC6E58E.12367.3389FE7@z.szalbot.lcwords.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 15/04/2010 11:08:14, Zbigniew Szalbot wrote:
> On 15 Apr 2010 at 8:30, Zbigniew Szalbot wrote:
>
>> Hello,
>>
>> I have the following lines in my /etc/newsyslog.conf
>>
>> /var/log/*-access.log 644 30 * @T00 JCG
>> /var/log/*-error.log 644 30 * @T00 JCG
>
> I added /var/run/httpd.pid at the end of both lines and will see if
> that helps.
I use this:
/var/log/httpd-access.log 644 3 100 * J /var/run/httpd.pid 30
/var/log/httpd-error.log 644 3 100 * J /var/run/httpd.pid 30
Signal 30 (SIGUSR1) causes Apache to do a graceful restart which is less
disruptive for anyone using the web site, but it can result in a few log
records being lost during the restart. If you're going to be running a
busy website, then it's better to use rotatelogs(1) (comes with apache)
or cronolog(1) (in ports) to cycle the log files. Neither of those
handles compressing or deleteing old log files, but a trivial cron job
will deal with that.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkvG6vkACgkQ8Mjk52CukIw4UgCfaMG9vpDTeMAvhCQ+MaBlgTEh
EbMAmgOI246i1nFgb7EuM6qVBbXqGVC8
=Tama
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BC6EAF9.7020002>