From owner-freebsd-current Wed May 21 12:19:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA29722 for current-outgoing; Wed, 21 May 1997 12:19:37 -0700 (PDT) Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA29713 for ; Wed, 21 May 1997 12:19:33 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.5/8.8.3) id WAA02595 for current@freebsd.org; Wed, 21 May 1997 22:19:16 +0300 (EET DST) From: mika ruohotie Message-Id: <199705211919.WAA02595@shadows.aeon.net> Subject: weirdoes... To: current@freebsd.org Date: Wed, 21 May 1997 22:19:16 +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 hmm... it seems i always catch the strange fishes... maybe i should dump my hardware. well, this is something i can actually reproduce, it's been around for at least few weeks now. at home, i run freebsd-current, last make world is from sunday nite, at work i run 2.2-stable, it's about two weeks old, though the prob, i think, cant recall anymore, were around before that 2.1-stable>2.2-stable upgrade... i use latest ssh from ports on both, 1.2.20, i always recompile it after make world. now, i hardly need to reboot the desktop at work, but every now and then i do, it's for development and testing. usually i just go to root xterm and do few sync's and reboot from it, i dont kill any xterms or ssh connections. _each_ time i do that, my home machine have rebooted at the same time, the ssh has been alive when i've ordered the work machine to reboot. almost equal setup that that desktop, the server at work, is also always ssh:ed, and is not rebooting. home machine is ppp connected, leased line. and as i said, i can reproduce this, with apparently 100% accuracy. ideas? or is this in category "twilight zone"? mickey