Dear fellow admins,
there were two quick responses.
Thanks to Daniel Monjar (Daniel.Monjar_at_orgtek.com) and Dr. Tom Blinn
(tpb_at_zk3.dec.com)
I quote the one from Dr. Thomas P. Blinn:
Those are what is known as "keep-alive timestamps". They are coming out of
the binlogd program; they were added during Revision 1.1.26.2 1998/09/22
18:49:22 to add support for a new processor/core logic family. It's not
clear to me (but I was not involved the planning or implementation) that
they are a useful feature; they eat up your disk space, and provide little
or no useful information for you (you usually know whether the system is
running, after all).
Apparently the new error log format specification (which doesn't apply to your
system as far as I can tell from the system type in the log record) requires
these; older log formats do not. It looks like the code generates them (every
10 minutes) whether you want them or not. I don't know whether there is a way
to configure binlogd so it does not generate them.
<snip>
Thanks,
Peter
Original message:
> Dear fellow admins,
>
> after patching DU 4.0E with the first Jumbo Patch (DUV40EAS00001-199902=
> 02) we
> have multiple entries like the following in the binary.errlog every day=
> (read
> with dia V2.9):
>
> ******************************** ENTRY 1 ***************************=
> =*=*=
>
> Logging OS 2. Digital UNIX
> System Architecture 2. Alpha
> Event sequence number 1687.
> Timestamp of occurrence 18-MAR-1999 11:21:59
> Host name seppel
>
> System type register x00000016 Alpha 4000/1200 Series
> Number of CPUs (mpnum) x00000003
> CPU logging event (mperr) x00000001
>
> Event validity 1. O/S claims event is valid
> Event severity 5. Low Priority
> Entry type 310. Time Stamp
>
> ******************************** ENTRY 2 ***************************=
> =*=*=
>
> Has anyone seen this, too?
Received on Thu Mar 18 1999 - 14:49:53 NZDT