Wierd Syslog statements

From: Brett C Helgeson (bhelgeson@csc.Cornell-Iowa.edu)
Date: 02/07/94


I was testing out some new commands and spells when I got a wierd
Syslog message. The first was a(see a below)then I got b(see below)

Mon Feb  7 19:05:31 :: EOF encountered on socket read.
Mon Feb  7 19:05:31 :: Losing descriptor without char.

Everything seemed to be ok after I got these messages, but I would 
like to know if something is going to go kaput on me or not..
Any info you could share would be appreciated. Thanks.. Brett@Legends...



This archive was generated by hypermail 2b30 : 12/07/00 PST