Re: [PLUG] huge /var/log

[Chuck Peters <cp@ccil.org>]

On Mon, 24 Sep 2001, Mike Leone wrote:

> how about tail -f /var/log/whichever-log-it-is? That'll show the last few
> lines.
>
> You could then maybe post at least that much here for us to try and analyze.

I just had a problem where syslog and kern.log was running about a gig per
day.

I fixed the problem and deleted the logs.  I just don't know why it was a
problem...  Can someone tell me why full duplex is a bad thing for a
network card?

The error in the logs point me to
linux/Documentation/networking/vortex.txt and I changed my other network
card to not run in full duplex.  The machine causing the problem has a
3com net card and was spewing junk in the logs.  The other machine has a
Kingston KNE20bt (ne driver) and I have had it set for full duplex for
years.

Here is the relavant part of linux/Documentation/networking/vortex.txt

Transmit error, Tx status register 82
-------------------------------------

This is a common error which is almost always caused by another host on
the same network being in full-duplex mode, while this host is in
half-duplex mode.  You need to find that other host and make it run in
half-duplex mode or fix this host to run in full-duplex mode.

As a last resort, you can force the 3c59x driver into full-duplex mode
with

        options 3c59x full_duplex=1

but this has to be viewed as a workaround for broken network gear and
should only really be used for equipment which cannot autonegotiate.


Thanks,
Chuck


______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug