mike@atc.SP.Unisys.COM (Mike Grenier) (01/22/91)
Subject: Re: '386 Unix Wars Newsgroups: comp.unix.sysv386 References: <350@metran.UUCP> From article <350@metran.UUCP>, by jay@metran.UUCP (Jay Ts): > In article <2812@cirrusl.UUCP>, dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi) writes: > > Judging from postings in this newsgroup, ESIX has fewer bugs or other > problems than ISC 2.2 or SCO UNIX. In working with ESIX, so far I haven't > run into any problems that I couldn't work around or solve either on my > own or with the help of ESIX tech support. They are responsive *and* > helpful both over the phone and by email. Judging from the experience of setting up a half dozen ESIX systems, I'll never buy from them again! Anybody (ISC, SCO, Microport) has less bugs. -Mike Grenier mike@cimcor.mn.org Subject: Re: Looking for a syslog that works in SysV3.2 land... Newsgroups: comp.unix.sysv386 References: <105@calcite.UUCP> From article <105@calcite.UUCP>, by vjs@calcite.UUCP (Vernon Schryver): > In article <81376@unix.cis.pitt.edu>, cgwst@unix.cis.pitt.edu (Gray Watson) writes: >> I am also looking for a "syslog-like" logging facility for SysV3.2 land that >> includes source. > > Using the toy STREAMS log mechanism in the SVR3.0 source might be an easier > IPC for kernel error logging. > The streams logging mechanism is called strlog() in the kernel. UNIX 5.3.2 systems should have /usr/bin/strace and /usr/bin/strerr which are used for kernel tracing (You can give it parameters for which driver you're tracing and level) and error logging (creates a log file in /usr/adm/streams). Of course the ESIX version of strerr dumps core when I call strlog out of the ST01 scsi driver....but what else is new. -Mike Grenier mike@sp.unisys.com mike@cimcor.mn.org