I noticed the following each night when syslog is running: (they are logged to the console)
Oct 15 19:14:16 newsyslog[258]: logfile turned over Oct 15 19:14:16 /kernel: syslogd: /var/log/cron: No such file or directory Oct 15 19:14:16 /kernel: syslogd: /var/log/maillog: No such file or directory Oct 15 19:14:16 /kernel: syslogd: /var/log/daemon: No such file or directory Oct 15 19:14:16 /kernel: syslogd: /var/log/security: No such file or directory Huh? - these files ARE there and they are fine. But even after a reboot..each night I see these. Sometimes it is the same file(s) each night and sometimes it is different. Everything rotates just fine, but these errors are weird. It is like syslogd is starting BEFORE the new files are created and hence dont see the file as actually being there! Any thoughts? -- J.D. Bronson Aurora Health Care // Information Systems // Milwaukee, WI USA Office: 414.978.8282 // Fax: 414.328.8282 // Pager: 414.603.8282 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
