Why sysklog uses its own logrotate and not logrotate script
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I would like to know why sysklog package uses its own logrotation
scripts and not logrotate.
Because it uses its own scripts, its rather tricky to configure. Eg its
impossible to have the first rotatet log (syslog.0) to be compressed.
According to the help test in the cron sysklog file there are reasons of
some possible open file handles.
but why not putting it in logrotate and reload sysklog ...
Reason for this is, I have a box that can make up to 1 gig log per day
and keeping that for one week means ~7gb, twice, ergo 14gb max ... and I
don't want to waste, nor can I give so much disk space away.
and before anybody asks, I already but all the things into logrotate. I
just curious why its not there from beginning.
lg, clemens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBf6qEjBz/yQjBxz8RArShAKDFIBFey42GyYDkcywAkjQKBwao3QCgv3HJ
rvvoKkkDfAo7ezciNFjlJ2M=
=raKX
-----END PGP SIGNATURE-----
Reply to: