SUMMARY: syslogd pile up on local host

From: Sean Coleman 497-5672 (coleman@boulder.nist.gov)
Date: Thu Dec 08 1994 - 17:32:17 CST


In a earlier request to the list, I asked why a large number
of syslogd's processes built up on my system when I did remote
logging.

John Stanley gave me the correct answer. When one logs out of
openwindows, it doesn't update the utmp file. If syslog is
suppose to send messages to a particular user logged into the
system and the user is logged out physically but utmp isn't updated,
the syslog process hangs.

Sean Coleman
NIST



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:16 CDT