Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!apollo!mishkin
From: mishkin@apollo.COM (Nathaniel Mishkin)
Newsgroups: comp.sys.apollo
Subject: Re: /etc/syslog goes wild??
Keywords: SR9.7
Message-ID: <4398c62e.1d6d5@apollo.COM>
Date: 2 Jun 89 21:37:00 GMT
References: <674@idacom.UUCP> <438f3c86.10b48@apollo.COM>
Reply-To: mishkin@jrst.UUCP (Nathaniel Mishkin)
Organization: Apollo Computer, Chelmsford, MA
Lines: 22

In article <438f3c86.10b48@apollo.COM> weber_w@apollo.COM (Walt Weber) writes:
>In article <674@idacom.UUCP> danny@idacom.UUCP (Danny Wilson) writes:
>>Our /etc/syslog.conf contains '1*/dev/log', so trying to 'catf'
>>/dev/log results in:
>>
>>	Error: unable to open file "log" - system (or process) crash 
>>	prevented complete file close.
>
>The extensible streams documentation (Open Systems Toolkit) discusses the
>32-byte streams header which precedes user data on files of type 'uasc'.
>The message above indicates that the /dev/log file has a corrupted
>streams header.  Change it's name so that you can create a new one, and
>syslogd will revert to it's normal, unobtrusive self...

Because this was always such a nuisance (and for other reasons) at sr10.x,
the default type of file ("unstruct" or "nil") doesn't have a 32 byte
header and hence you tend not to see this problem any more.

-- 
                    -- Nat Mishkin
                       Apollo Computer Inc., Chelmsford, MA
                       mishkin@apollo.com