[OpenAFS] Proposed changes for server log rotation

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9802E40F8AD4B2185BE05322
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/2/2010 10:22 PM, Michael Meffie wrote:
>> If the wish list is open, the ability to log to a pipe so that one
>> could use a tool such a cronolog would be convenient for us.
>=20
> Hello David,
>=20
> Yes, logging to a pipe is already possible, and what I'm
> suggesting would not change that. And, as others have mentioned,
> logging to syslog is also already possible, and even preferred
> by many sites.
>=20
> The key point is that currently some sites may be relying on
> weekly restarts and the current rename from FileLog to FileLog.old
> to avoid filling a disk partition. I think a more sensible approach
> in long term, for sites that choose to log to regular files,
> is to just let the server append, and let the modern log rotate
> tool of your choice deal with the log rotation.

Of course that requires that there be a log rotation tool.
I don't think that OpenAFS by default should fill the disk partition
simply because it is permitted to run for years without restarts
and the admin has not configured a log rotation tool.

Since 1.6 is disabling weekly restarts by default, this problem
should be addressed before its release.

Jeffrey Altman



--------------enig9802E40F8AD4B2185BE05322
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJM+GTtAAoJENxm1CNJffh4o4MIAMvKFcknuTm2n3HDBmt3eSZS
YloFtJ0c4WMCoFpaDMVucLJicXzg2BbQbzZkCPLijXotojBHhVuC/4gouzxc600B
2GElHNptPaqqZx7iBZrXwSU3LBgN421KJh+l1VS3bP9oB82MlwjEHW8VrX+YukSR
N16iy42JO24hyjyaaOT0FrAwFc0smIypYzi/erOjEsuCi++QucIeXSUGYSkA5ZOa
4qvM9Q4QFcoL5Bg7mcLYwE6BiNcbfqMKKv/McrQnjL2TSFa+Ua4azYQ3dtrmrui5
dz29De3M/kzR1EsmHLSq5Kxl3h6wzSXKHXHLGVTqbH8SsUhpvEBjS0qymuvw4eg=
=4Jyw
-----END PGP SIGNATURE-----

--------------enig9802E40F8AD4B2185BE05322--