MATHRICH@umcvmb.missouri.edu (Rich Winkel UMC Math Department) (06/17/89)
Has anyone seen this: For no apparent reason, the cpu performance meter starts pegging out. PS indicates that syslogd is hogging 90%+ of the cpu. Rebooting seems to be the only fix. Help? Rich
m2@insyte.UUCP (Mike Arena) (06/29/89)
In article <1221@bnlux0.bnl.gov> abrams@max.UUCP (The Ancient Programmer) writes: >In article <20036@adm.BRL.MIL> MATHRICH@umcvmb.missouri.edu (Rich Winkel UMC Math Department) writes: >>Has anyone seen this: For no apparent reason, the cpu performance meter >>starts pegging out. PS indicates that syslogd is hogging 90%+ of the cpu. >>Rebooting seems to be the only fix. > > Check your /etc/syslog.conf file. The first line must be > define(LOGHOSTS, 1) ^ >If it's not, syslog will hog the cpu. There is a bug in the 4.0 build procedure >that fails to insert this line. This is documented somewhere, but I can't >recall where at the moment. I tried define(LOGHOST,1) and that seemed to work after sending the syslogd process the HUP signal. But I did get a message saying that there was no /var/log/syslog file. Is this undesirable? However, I could not find this in the documentation. I looked at syslogd(8) and syslog.conf(5) but no luck. I am very new to system administration on Sun computers (we have a 4/110 with SUN OS 4.0.1) so I would like to find out more useful tidbits like the one above. -- Michael J. Arena (617) 965 8450 | UUCP: ...harvard!linus!axiom!insyte!m2 Innovative Systems Techniques | ...harvard!necntc!lpi!insyte!m2 1 Gateway Center, Newton, MA 02158 | ARPA: insyte!m2@harvard.harvard.edu
abrams@max.bnl.gov (The Ancient Programmer) (07/23/89)
In article <20036@adm.BRL.MIL> MATHRICH@umcvmb.missouri.edu (Rich Winkel UMC Math Department) writes: >Has anyone seen this: For no apparent reason, the cpu performance meter >starts pegging out. PS indicates that syslogd is hogging 90%+ of the cpu. >Rebooting seems to be the only fix. > >Help? >Rich Check your /etc/syslog.conf file. The first line must be define(LOGHOSTS, 1) If it's not, syslog will hog the cpu. There is a bug in the 4.0 build procedure that fails to insert this line. This is documented somewhere, but I can't recall where at the moment. <karl> INTERNET: abrams@bnlux0.bnl.gov BITNET: abrams@bnlux0.BITNET UUCP: ...philabs!sbcs!bnlux0!abrams