okay. I'll find time to try the next version.
Meanwhile, isn't it possible to use newsyslog instead of clog?
Scott Ullrich <[EMAIL PROTECTED]> wrote:
Scott Ullrich <[EMAIL PROTECTED]> wrote:
Hopefully this is fixed in the next version. We where launching
tcpdump again when it was already running really working the log
system out.
Scott
On 7/12/05, Albert Miles Enabe <[EMAIL PROTECTED]>wrote:
> pfsense 0.69.10 still causes 100% CPU usage after clearing Firewall Log and
> syslogd process uses more than 90% of this.
>
> It seems that there is an anomally somewhere during the reinitialization of
> the /var/log/filter.log file by the clog command that causes syslogd to
> consume that cpu time.
>
> I have a hunch that
> 1.) the file generated by clog (with -i -s options) has incompatible format
> for syslogd or
> 2.) syslogd is 'unhappy' with the sudden change in the file
> /var/log/filter.log by another application like clog especially with a high
> volume of messages being logged
>
> I have not tested the other log files yet and I haven't performed a tcpdump
> output for syslogd packets during this event..
>
> Hope this helps.
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
