On Apr 1, 2008, at 9:26 PM, Jerry Krinock wrote: > > On 2008 Apr, 01, at 16:37, Richard Hartman wrote: > >> 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. > > If this is Mac OS 10.5, I would add that I too have started > "imagining" weird things in the new and improved Console for > Leopard. Example: I do something which should create a log entry, > look in Console.app, clear out the "Filter" field and see nothing. > Reload. Sometimes that brings up the expected entry. Other times, > I wait 2 minutes, reload again, and it appears. > Yes, OS 10.5.2 on an intel iMac. Although I can't prove it since I did a reboot, Eric Christ has convinced me that my recent bizarre episode was probably caused by syslogd taking a powder... >> Note: This is NOT an April Fool's joke (unless somebody at Apple >> programmed this log silence to mess with terminal noobs). > > It's just not repeatable enough to be sure that I'm not imagining it > just yet. > I have to admit to noticing some other sporadic console weirdness, but had also chalked it up to my imagination. Richard