Is log_in_vain really good or really bad?

[Jason DiCioccio]

I've actually seen something similar happen.  What happens, is when syslog 
gets backed up with lots and lots and lots of messages, it leaks a couple 
via wall.  I'm not sure why, but I've seen it happen.  Usually you only 
receive a fragment of a log entry.  Perhaps it's a bug in syslogd, but it's 
only occurred maybe 2-3 times with me, so I just wrote it off.

Regards,
-JD-

--On Sunday, April 18, 2004 7:12 PM -0700 "Crist J. Clark" 
<cristjc at comcast.net> wrote:

> On Sat, Apr 17, 2004 at 04:28:35PM +0200, z3l3zt at 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" occurred 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 at alum.mit.edu
>                                    |     cjclark at jhu.edu
> http://people.freebsd.org/~cjc/    |     cjc at freebsd.org
> _______________________________________________
> freebsd-security at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-security
> To unsubscribe, send any mail to
> "freebsd-security-unsubscribe at freebsd.org"