On Thu, Jun 05, 2008 at 05:49:12PM -0700, Jyri Virkki wrote: > Dean Roehrich wrote: > > > > > > The two issues remaining to be addressed in this case are: > > > > 1) Some note linking logadm(1m) to logrotate(1m). We chose Nico's > > recommendation from mid-day yesterday to update the SEE ALSO section in > > logrotate(1m). > > I'm not holding the case up for it but I sure would like if it can > also include an explanatory comments in the distributed logrotate.conf. > > The main target user for the familiarity of logrotate is, well, > familiar with it already so they won't be reading the manpage so the > comment there will be missed. > > Which will in some cases lead to an annoyed customer and costly > support calls when they call Sun trying to figure out what mysterious > force is messing up with the log files that logrotate is handling. > > If I was doing this case I'd add something like this to the top of the > config file (possibly spending some more time polishing the wording if > I was doing the putback..) > > > # Note: logadm(1M) is the default and recommended log rotation tool > # in OpenSolaris. By default it is being invoked from the crontab of root. > # If enabling logrotate, either avoid configuring it to manage the same > # logfiles are logadm or disable logadm, to avoid conflicts.
I've asked Colin to incorporate this change. Dean
