> > > A few minutes ago NNTPcache 2.2b5 (parent process) here started consuming > > > all CPU resources, at about the same time syslogd did, which suggests to > > > me that there was some frantic logging going on (not that any of our logs > > > showed any). > > > > Are you logging debug messages? > > I was, before I had to kill the syslog process to restore some form of > sanity on the machine. There was nothing showing up in the logs that was > out of the ordinary, but the syslog daemon and parent NNTPcache processes > were going ballistic. > > My syslog daemon clocked up 2 hours CPU time in 12 hours today. Since > commenting out the news facility, it's clocked about 2 seconds in 4 hours. > News logging is local - the rest is to a central server. the better way to deal with this is to tell nntpcache to not log debug messages. it's still sending them down the pipe otherwise. the full debugging set will dump a heftly quantity of information. Cheers, Julian.
