1834465 Members
2879 Online
110067 Solutions
New Discussion

syslogd and QPK1100

 
Bill_15
Contributor

syslogd and QPK1100

Have there been any problems with the syslog daemon and the September `01 Quality Pack Bundle? syslogd has been utilizing more than 50% of the CPU, and I haven't even had any syslog entries in the past 8 hours. This problem didn't manifest until after I installed the QPK Bundle a week ago.
2 REPLIES 2
Jeff Schussele
Honored Contributor

Re: syslogd and QPK1100

Hi Bill,

None that I'm aware of.
I'd bounce the syslogd daemon.
Determine the PID of the daemon & kill -HUP it.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Michael Tully
Honored Contributor

Re: syslogd and QPK1100

Hi,

There has been no update to syslogd for some time. I agree with Jeff, stop and restart the process. From the syslogd man page

To kill syslogd, send it a terminate signal:

# kill `cat /var/run/syslog.pid`

To make syslogd, re-read its configuration file, send it a HANGUP signal:

# kill -HUP `cat /var/run/syslog.pid`
Anyone for a Mutiny ?