From owner-freebsd-stable Sun Dec 30 16:42:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shemp.palomine.net (shemp.palomine.net [216.135.64.135]) by hub.freebsd.org (Postfix) with SMTP id C86E737B405 for ; Sun, 30 Dec 2001 16:42:46 -0800 (PST) Received: (qmail 7001 invoked by uid 1000); 31 Dec 2001 00:42:34 -0000 Date: Sun, 30 Dec 2001 19:42:34 -0500 From: Chris Johnson To: Brian McDonald Cc: David Malone , stable@FreeBSD.ORG Subject: Re: syslogd blocking => can't su to root Message-ID: <20011230194234.A6955@palomine.net> References: <20011230173548.A58662@walton.maths.tcd.ie> <20011230133123.W2949-100000@nivomede.internal.lustygrapes.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011230133123.W2949-100000@nivomede.internal.lustygrapes.net>; from brian@lustygrapes.net on Sun, Dec 30, 2001 at 01:59:03PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Dec 30, 2001 at 01:59:03PM -0500, Brian McDonald wrote: > The boxes I've noticed this on are 4.1-RELEASE boxes. Kernel configs are > essentially GENERIC with devices removed that aren't present on the system > (eisa, scsi cards, net cards, etc). Both have IPFIREWALL. One runs named > and sshd, the other runs named, sshd, and postfix. At the time of the > failures, both ran syslogd with the -s argument. Nothing really out of > the ordinary except for the fact that both have been running for a year > and half straight. (okay, on BSD that isn't out of the ordinary.) Both > are hooked up to a Belkin KVM - can a twitchy ps2 mouse/keyboard irritate > the console driver? Ours is also connected to a KVM switch, and that switch uses the scroll lock key to bring up a menu of machines it's connected to (I've never seen it, but that's how it was described to me). Someone else suggested that maybe scroll lock was on on the first virtual terminal, causing the console to block. This seems likely to be the cause of the problem, and I'll have someone check it out when the office opens back up after the holiday. Chris --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8L7R5yeUEMvtGLWERAnH8AJ4ldB/5EOXtmIdZi8weSTvIWVTynQCffnbP 6miA+lLRNP3FFowmPbOOVmA= =7Fyo -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message