[X4U] Re: Time Warp Hits System Logs

[Richard Hartman]

This was sent by accident to this list instead of the x-unix list;  
apologies.

Still, the likely resolution is instructive; one of the x-unix gurus  
(Eric Christ) suggested the probable culprit: the system logging  
daemon (syslogd) likely got clobbered somehow. It can be restarted  
using the terminal, or for the terminal-phobic, re-activated by a  
reboot.

Now, back to your normal programming...

Richard
=================
> From: Richard Hartman <seasoft at west.net>
> Subject: [X4U] Time Warp Hits System Logs

> .
.
snip
.
.

>
> The thing is that All the console and system logs quit getting updates
> at that instant. I just noticed this while I was looking at the system
> log out of boredom. I was unable to do anything that would generate a
> log update (for example, I initiated a Time Machine backup which
> normally always reports progress to system; nothing). I rebooted the
> system and the log entries began to update normally. Here is the
> system log portion spanning the "missing" 5+ hours:
> .
.
snip
.
.

>
> How in blazes can the logs go completely silent for so long with no
> observable operational consequences? Has anyone here seen such
> behavior? Should I be concerned? I am really, really confounded by  
> this.
>