Syslog takeover
D. Whiteley
whiteley at nadc.arpa
Mon Jul 10 23:37:09 AEST 1989
>From: metaware!riscy!adam at ucscc.ucsc.edu (Adam Margulies)
>
>syslog seems to like to take over a system from time to time and
>eat 80% of the cpu time. It writes nothing to /usr/adm/messages
>so I can't tell if it is doing it for good REASON or anything.
>how can i free myself from it, other than turning it off all together?
If you're running SunOS 4.0, in the READ THIS FIRST document that came
with the manuals, there's a paragraph about what to do to fix this
problem. It says:
The symbol LOGHOST is not correctly defind by syslogd on loghost machines.
This results in 100% CPU usage and syslogd accumulating large amounts of
CPU time. To prevent this problem insert the following line at the
beginning of the /etc/syslog.conf on loghost machines:
define(LOGHOST, 1)
Hope this helps,
Denice
whiteley at nadc.arpa
More information about the Comp.sys.sun
mailing list