You are really blowing it by leaving those .0 files around or expecting users will look in some README.
E.g., today I did grep bla syslog. Not there? Must be in syslog.0, not there either. So I told my assistant "the bla problem didn't occur this morning, hooray!" when all along it was lurking in syslog.1! Therefore when a user installs rsyslog, for each .0 found, you should rotate all the logs and move the .0's into the new_names.1.(gz?). You don't even need a warning screen to tell the user what is happening. So how should I clean up the current mess, # find . -name \*.0* -printf %f\\n boot.0 syslog.0 Xorg.0.log daemon.log.0 mail.warn.0 dmesg.0 debug.0 user.log.0 lpr.log.0 messages.0 mail.err.0 mail.log.0 kern.log.0 auth.log.0 mail.info.0 Xorg.0.log.old remove them? But not all are logs that rsyslog is in charge of? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
