From owner-freebsd-current  Mon Apr  7 01:28:11 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA00990
          for current-outgoing; Mon, 7 Apr 1997 01:28:11 -0700 (PDT)
Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00981
          for <current@freebsd.org>; Mon, 7 Apr 1997 01:28:08 -0700 (PDT)
Received: (from bsdcur@localhost)
          by shadows.aeon.net (8.8.5/8.8.3) id LAA01124
          for current@freebsd.org; Mon, 7 Apr 1997 11:28:34 +0300 (EET DST)
From: mika ruohotie <bsdcur@shadows.aeon.net>
Message-Id: <199704070828.LAA01124@shadows.aeon.net>
Subject: goose chase...
To: current@freebsd.org
Date: Mon, 7 Apr 1997 11:28:34 +0300 (EET DST)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

well...

i might be after wild gooses here, but i have a reason to believe
windows 95 telnet is able to cause something weird on my -current
machine, problem started about 2 weeks ago, it might've been
caused by me implementing /etc/login.conf but i'm not sure. (yes, yes,
i didnt have that, or /etc/sysconfig for a _long_ while, byt finally
took the whole machine into the _truly_ current stage)

reason i report this is if anyone else is having weird things also...

the symptoms are from slow as hell performance on the telnet window (on
that win95) and occasionally it reboots! the bsd. (with different
kernels, been updating those rather often)

i didnt think that's possible until today when i found out it is not only
the ether connected win95 that can make this, but also a remote win95
telnetting into the machine thru ppp0 from random machine.

and it's only? those win95 telnets that cause this, i constantly ssh
and other people telnet from where-ever and i dont see probs with that.

sure, it could be, and most likely is win95 prob, but why did it appear
only now? assuming it did appear. it also might not have anything to
do with the telnet, but i believe i managed to generate the reboots
to _bsd_ that way. it appeared to reboot after similar things on the win95
end, but it might've been only coincidence. i'd be shrugging this off if
it would not be my _bsd_ that it reboots?.

i have a 67 meg vmcore.0, but i dont know what to do with it... =)
(gdb tells me my kernel.0 and vmcore.0 are unknown format)


mickey