Log archiving question

[Matthew Seaman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Walt Pawley wrote:

> I've had no difficulties with the change made on my Mac OS X
> Jaguar system - if it affects something, the something is
> something I apparently don't do. So, all that preamble brings
> me to my question. Are there things that modifying the archived
> log data file names would interfere with?

There shouldn't be -- the archived log files are only there for
reference.  Any live logging action should go to the base (unnumbered)
log file.

However, it is possible to get into a state where a program is 
logging to a file that has no directory entry -- the symptoms there
tend to be /var filling up according to df(1) but with plenty of
space left according to du(1).  That happens when the process doing
the logging does not get signalled to close and reopen the log file
- -- newsyslog will signal processes for you, but it defaults to
signalling syslogd in the absence of any other instructions.

	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 v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHf2Yt8Mjk52CukIwRCLfoAJ91oGyEKOsXtgwdBq8RoOyfx8+f4gCgiQQA
cAQWIYASzkgVf0MZRJoAnV8=
=QYkv
-----END PGP SIGNATURE-----