On Thu, Jun 05, 2008 at 04:24:08PM +0100, Ceri Davies wrote: > On Thu, Jun 05, 2008 at 07:24:05AM -0400, James Carlson wrote: > > Nicolas Williams writes: > > > On Wed, Jun 04, 2008 at 09:21:52PM -0700, Jyri Virkki wrote: > > > > - Already knows how to use it so goes ahead and sets it up (doesn't need > > > > to read the manpage) > > > > > > "Sets it up" -> edit root's crontab? > > > > Do you mean to say that installing the package doesn't automatically > > do that, so the software is usable out of the box? That'd be a shame.
How can the package know what times I want logrotate to run at? (Yes, I know, the same applies to logadm, which runs at 3:10AM every day.) The audit system is more dynamic than this, and I must say I prefer that approach. > I'm not sure how the packager would have any idea what logs I might be > interested in rotating. I don't expect installing the StarOffice > packages to update my CV for me :) Presumably it would install a config file that rotates no logs but still install the cronjob. So then I think we want a warning about logadm in the logrotate config file and in the logrotate manpage. Perhaps a warning about logrotate in logadm's manpage and /etc/logadm.conf would also be appropriate.
