From owner-freebsd-stable Mon Oct 9 7:30:20 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [205.252.34.9]) by hub.freebsd.org (Postfix) with ESMTP id C4B3537B503 for ; Mon, 9 Oct 2000 07:30:16 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [205.252.34.3]) by yertle.kciLink.com (Postfix) with ESMTP id 5C13C2E449 for ; Mon, 9 Oct 2000 10:30:16 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.0/8.11.0) id e99EUGj89047; Mon, 9 Oct 2000 10:30:16 -0400 (EDT) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14817.54904.257674.7378@onceler.kciLink.com> Date: Mon, 9 Oct 2000 10:30:16 -0400 (EDT) To: stable@FreeBSD.ORG Subject: Re: curious interaction between kdm and snmpd on startup In-Reply-To: References: <14814.15644.780542.774320@onceler.kciLink.com> X-Mailer: VM 6.72 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DW" == Doug White writes: DW> This is what happens when the getty on console and xdm start up DW> simultaneously. The keyboard goes into limbo-mode. That explains it... wow. What a fun timing issue. Curious how adding snmpd to startup triggers it every time! DW> The solution is to get xdm to wait 5-10 seconds for the getty to launch DW> before starting itself. This can be done with some nifty shell Yes; this is what I'm doing now: (sleep 30; kdm) & but I think I can cut the sleep time a bit ;-) Thanks for the tip and confirmation. Perhaps I can just start kdm from init (/etc/ttys) and it will work out the timing itself ... I'll try that later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message