Linuxconf logrotate.d entries need missingok or equivalent in them; if
you never use linuxconf, root will still get mailed his dosage of errors..
The %post script for linuxconf creates these logs, so they're there.
Clean install is fine; upgrade is not.
After an _upgrade_ of RH60 and/or RH62, I got mails like:
errors occured while rotating /var/log/htmlaccess.log
stat of /var/log/htmlaccess.log failed: No such file or directory
errors occured while rotating /var/log/netconf.log
stat of /var/log/netconf.log failed: No such file or directory
# rpm -V linuxconf
SM5....T c /etc/conf.linuxconf
This might be caused by the fact that in RH6x, those files are in package list,
but in betas they should be touched in post-install.
Okay, that's bad, because that means an older version of the package
is *removing* that file on uninstall. I'll have to add a trigger to get around
Trigger should be in linuxconf-1.19r1-9 and later.