From owner-freebsd-stable Fri Oct 6 13:59:11 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 8AD4237B502 for ; Fri, 6 Oct 2000 13:59:09 -0700 (PDT) Received: from onceler.kciLink.com (onceler.kciLink.com [205.252.34.3]) by yertle.kciLink.com (Postfix) with ESMTP id D6D782E443 for ; Fri, 6 Oct 2000 16:59:08 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.0/8.11.0) id e96Kx8s04406; Fri, 6 Oct 2000 16:59:08 -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: <14814.15644.780542.774320@onceler.kciLink.com> Date: Fri, 6 Oct 2000 16:59:08 -0400 (EDT) To: stable@freebsd.org Subject: curious interaction between kdm and snmpd on startup 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 I run kdm from my /etc/rc.local script to get nice graphical login to KDE. Recently I added ucd-snmp to this system. Today I did a reboot after testing the vmware "vmnet" module which happened to lock up my kernel. Upon reboot, the keyboard within X under the kdm session was non-responsive to most keystrokes. The CTRL-ALT-Fn sequence beeped at me execpt for F2, which didn't do anything. CAPS LOCK worked, as did NUMLOCK. The regular keys did nothing. All I could do was CTRL-ALT-DEL to get out of it. Disabling kdm from the boot and running it manually after the rest of the system came up worked fine. Finally, I noticed that during a boot-up, right after snmpd was started, the screen mode switched to X. Not until after I hit the C-A-D reboot sequence did the remainder of the text from the boot appear. If I disable snmpd from the boot sequence, I briefly see a flash of a login prompt before the X screen switch, and everything works fine. Is there some interaction going on with the startup scripts and snmpd and kdm? Any ideas on how to work around this other than manually running snmpd after I boot up? Thanks. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message