gomer:/logs# tail syslog*
Jun 7 08:00:00 gomer in.cfingerd[3139]: refused connect from 207.82.13.209
Jun 7 12:47:55 gomer sendmail[68]: NOQUEUE: SYSERR(root): getrequests:
accept: No route to host
Jun 7 12:48:00 gomer sendmail[68]: NOQUEUE: SYSERR(root): getrequests:
accept: No route to host
Jun 7 13:16:47 gomer sendmail[68]: NOQUEUE: SYSERR(root): getrequests:
accept: No route to host
Jun 7 13:17:32 gomer last message repeated 4 times
Jun 7 17:39:50 gomer kerneld: error: No such file or directory
Jun 7 17:40:21 gomer last message repeated 622 times
Jun 7 17:40:26 gomer last message repeated 650 times
Jun 7 17:42:45 gomer last message repeated 5 times
Jun 7 17:43:19 gomer last message repeated 614 times
gomer:/logs# date
Fri Jun 7 17:16:44 EDT 1996
What the hell is with the reported log times? The system clock was
indeed in sync with the current real time. This is the first time I've
noticed this type of situation. Perhaps its attempting to predict the
future.
I'm not sure what version of syslogd I'm using except that it came from a
Slackware 3.0 installation. This is with Linux kernel 1.99.14.
Greg.