Date: Mon, 19 Apr 2004 11:59:34 +0200 (CEST) From: "Jesper Wallin" <z3l3zt@hackunite.net> To: "Eugene Grosbein" <eugen@kuzbass.ru> Cc: freebsd-security@freebsd.org Subject: Re: Is log_in_vain really good or really bad? Message-ID: <2711.213.112.193.91.1082368774.squirrel@mail.hackunite.net> In-Reply-To: <4083A0C2.3F86159E@kuzbass.ru> References: <1998.213.112.193.35.1082212115.squirrel@mail.hackunite.net> <20040419021239.GA67288@blossom.cjclark.org> <4083A0C2.3F86159E@kuzbass.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> "Crist J. Clark" wrote: >> >> On Sat, Apr 17, 2004 at 04:28:35PM +0200, z3l3zt@hackunite.net wrote: >> [snip] >> >> > My server box is a Intel Celeron 733Mhz, 384Mb of RAM.. yet it's slow from >> > time to time since I only run ATA66 due to the old motherboard. When this >> > "attack" occured yesterday, the box almost died and the box were working >> > 100%.. all users who were logged in got "spammed" since the default >> > *.emerg in /etc/syslog.conf is set to "*" .. >> >> Not sure what that has to do with anything. The log_in_vain messages get >> logged at "info" level. What messages were your users seeing? >> -- >> Crist J. Clark | cjclark@alum.mit.edu > > I believe that was a bug in syslogd and this bug is already fixed > in both of CURRENT and STABLE for not so long. > > Eugene > Fixed you say.. I run FreeBSD 5.2.1-RELEASE-p5, yet it's there.. Regards, Jesper Wallin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2711.213.112.193.91.1082368774.squirrel>