-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm wondering if I can safely use newsyslog with a newsyslog.conf with these lines in it:

/var/log/httpd/access_log/*            644  1     *    $W0D0 G
/var/log/httpd/error_log/*             644  1     *    $W0D0 G
/var/log/httpd/ssl_request.log         644  1     *    $W0D0
/var/log/httpd/error.log               644  1     *    $W0D0
# After this point should be one line...
/var/log/httpd/access.log              644  1     *    $W0D0 -     
/var/run/httpd.pid 30

or if not, what should I do instead?

(I have 4 separate vhosts that keep their access logs in the first 2 directories)

For the record, I want weekly rotation on Sundays at midnight (I assume JST, since I have my time set to local time, which is JST [GMT+9, no DST]), keeping 1 log, (the way I read the fine manuals, I'll have to have a cron job bzip2 it up later and move it aside if I want to keep more and/or compress them) permissions 644 with the owner being root:wheel, no size check, and the last part of the last line should send a SIGUSR1 (30) signal to Apache, which should do the equivalent of a 'apachectl -k graceful' per http://httpd.apache.org/docs/2.2/stopping.html.

My question really is, does newsyslog send the signal at the right time [after the rotation is done, per http://httpd.apache.org/docs/2.2/logs.html#rotation] and does it do the lines in order???)

- --Curtis

- -- Curtis Jewell
[EMAIL PROTECTED]

"Killed enough? ... Yes, Your Highness, I think we all have."
  --John Patrick Ryan (from 'The Sum Of All Fears', Tom Clancy)

[I use Pine, which deliberately does not display colors and pictures
in HTML mail]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFS6ByvCi+150VKIMRAs6PAKDOOvnARxXKUTY5dvNrob3gl9+aZACdG+P+
Uz0GrVe1p5MNuRPwiTbBXxY=
=lTB2
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to