----- Original Message -----
From: Craig Foster <[EMAIL PROTECTED]>
Sent: Tuesday, March 27, 2001 9:16 AM
Subject: RE: [e-smith-devinfo] Corrupted [messages] Log Files
> In mc, use edit (F4key) to read the previous logs.
>
> Craig Foster
Thank-you... Yep, that did it!
However, now that we can -read- the older logs
(more easily), we see that the problem of mixed
dates was happening earlier on...?
The mystery continues...
If we don't determine that it was caused by some
verifyable instrustion or something we can fix,
we'd be shy about taking an e-smith 4.1.1 to mkt.
Ideas? Suggestions? Has anybody else experienced
anything like this? If so, how was it resolved?
TIA
> -----Original Message-----
> Sent: Tuesday, 27 March 2001 6:43 AM
> Subject: [e-smith-devinfo] Corrupted [messages] Log Files
<snip>
> date-time stamps
> -not- in order, as one reads down any one log...
>
> E.g. dates might appear (in small batches) in this
> order, using our most recent 'messages' log as an
> example (summary below, reply for copy of the
> whole messages[.unx] log file):
>
> Mar 26's (syslogd ... restart...)
> Mar 26's (kernel logs DENY's - lots... maybe an intrustion...?)
> Mar 27's (OK)
> Mar 27 01:01 about an hour since prev entry (kernel log DENY ppp0)
> Mar 4's a batch from 23:54 syslogd restart... apparently after a
> re-boot!
> Mar 4's a batch from 23:53 ('rc: starting syslog' & 'rc.sysinit' at
> interface)
> Mar 5's (OK... until... last in batch is time-stamped 00:01)
> Mar 4 13:31 (just 1 - 'named shutting down')
> Mar 5 00:01 (just 1 - 'e-smith running event handler)
> Mar 4 13:31's (several, starting with some fr. named, now starting
> again)
> Mar 5 00:01's (pppd noticing a disconnect...)
> etc.
>
> (a slightly sanitised ver of this 'messages' available on request...)
> Mar 27's (ntpdate [1624] step time server...)
>
> While dates of messages[.n] -files- are also (-this- time) OK:
>
> messages Mar 27
> messages.1 Mar 26
> messages.2 Mar 4
> messages.3 Mar 3
>
> they have - in previous times - been a bit rearranged.
