Re: dropping network connection
Well, it turns out that it's a hardware bug with the auto-sensing ethernet
port built into the motherboard used in the beige G3's. The ethernet
controller polls the nearest hub/switch to find out whether the network is
10/T or 100/T. The hub responds, but the controller decides before
getting teh response that the network is simply down, and shuts off.
So it looks like I'm goin' PCI on this particular box...
Thanks for the suggestion, though...I'm gonna save it in case other
problems crop up.
PS the .sig is from the book "A River Runs Through It" by Norman Maclean
On Sun, 1 Jul 2001, Joost Kooij wrote:
> On Sat, Jun 30, 2001 at 11:44:16PM -0400, Ian Marlier wrote:
> > So I'm wondering if anyone has thoughts/ideas why this might have
> > happened, and how I might go about fixing it...
> You'll need to know what needs fixing first. If you're unlucky,
> it is something like an endianness bug in a nic driver in the kernel.
> Set a cron job that gathers some stats on the box every minute,
> 5 minutes or hour.
> Make it write the output of:
> cat /proc/interrupts
> cat /proc/loadavg
> cat /proc/meminfo
> cat /proc/slabinfo
> cat /proc/stat
> /bin/netstat -atpn
> /bin/ps auxwwf
> to a file "stats.yyyymmdd.hhmmss" in a dedicated directory.
> Watch this going for a while, you knwo how much diskspace this
> is going to eat if left running unmonitored for extended periods
> of time. Maybe you need to add another weekly or daily cron job
> that removes or gzips older logfiles.
> > Eventually all things merge into one, and a river runs through it.
> > The river was cut by the world's great flood and runs over rocks from
> > the basement of time. On some of the rocks are timeless raindrops.
> > Under the rocks are the words, and some of the words are theirs.
> > I am haunted by waters.
> Nice .sig, where does it come from?
773 667 2550 (home)