> > From: Paul Courry <[log in to unmask]>
> > To: [log in to unmask]
> > Subject: LOG process terminated, no system logging
> > Date: Thursday, May 27, 1999 2:20 AM
> >
> > Ran into a new one for me, predictive support informed me that system
> logging, shown as LOG, process 39, priority BS 50
> > stopped on it's own. It showed as an active process with no CPU time
> being used, no records being added to the LOG5527 file
> > and the file still showed as open under Listf and SOS by Lund.
> >
> > Since we couldn't reboot (24x7 operation, this HP runs a semiconductor
> manufacturing operation, rebooting is *expensive*), HP
> > went in with DEBUG and tweaked RAM to reenable logging.

AFAIR, a known issue are programs opening the current logfile
with mapped access. Suspicious would be any auditing software
that analyses logfiles. The most well known vendor - VESOFT -
has AFAIK fixed that quite a while ago.

Goetz.