Date: Mon, 27 Mar 2006 22:59:16 +0400 (MSD) From: Maxim Konovalov <maxim@macomnet.ru> To: "Michael W. Lucas" <mwlucas@blackhelicopters.org> Cc: hackers@freebsd.org Subject: Re: syslogd not draining Message-ID: <20060327224826.U89207@mp2.macomnet.net> In-Reply-To: <20060327184643.GA58674@bewilderbeast.blackhelicopters.org> References: <20060327160130.GA57689@bewilderbeast.blackhelicopters.org> <20F3E06D-5727-4531-A81B-DF64765D1564@SARENET.ES> <20060327173841.GA58274@bewilderbeast.blackhelicopters.org> <20060327214209.U87890@mp2.macomnet.net> <20060327181501.GA58448@bewilderbeast.blackhelicopters.org> <20060327222836.J89207@mp2.macomnet.net> <20060327184643.GA58674@bewilderbeast.blackhelicopters.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[...] > > ~100 datagrams per second, not a lot. Perhaps they are huge. > > Not that I've noticed. It's syslogd, DHCP, DNS, and flow-capture > from a variety of devices, all generally small packets. I know nothing about your netflow setup but it can generate a huge amount of udp traffic. Check 'pkts' and 'lost' fields in /var/log/flow-capture. > > > > How much cpu time does syslogd use? > > > > > > Not much. ps -ax | grep syslog gives: > > > > > > 4317 ?? Ss 0:01.60 /usr/sbin/syslogd -l /var/run/log -l > > > /var/named/var/run/log > > > > Try to remove a log socket for named and restart syslogd. > > Removed the named socket and restarted. We'll see what happens. [...] Can you check there is nothing from syslogd on the serial console? -- Maxim Konovalov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060327224826.U89207>