From owner-freebsd-questions@FreeBSD.ORG Thu May 27 14:56:35 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFF63106567B for ; Thu, 27 May 2010 14:56:35 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail4.sea5.speakeasy.net (mail4.sea5.speakeasy.net [69.17.117.48]) by mx1.freebsd.org (Postfix) with ESMTP id CAEB58FC0A for ; Thu, 27 May 2010 14:56:35 +0000 (UTC) Received: (qmail 15813 invoked from network); 27 May 2010 14:56:35 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail4.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 27 May 2010 14:56:35 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id E22015082F; Thu, 27 May 2010 10:56:33 -0400 (EDT) From: Lowell Gilbert To: n dhert References: Date: Thu, 27 May 2010 10:56:33 -0400 In-Reply-To: (n. dhert's message of "Thu, 27 May 2010 15:59:22 +0200") Message-ID: <44pr0h2y1q.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: getty repeating too quickly port /dev/ttyv8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 14:56:36 -0000 n dhert writes: > I upgraded a FreebSD 7.2 to 8.0. That system had KDE and KDM as window > manager. > Now, after rebooting I get two messages on the console > init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs. > > I can login at the console in text mode (Ctrl-Alt-F1, F2, ... F8), > Ctrl-Alt-F9 does not do anything but giving that getty repeating ... error > My /etc/ttys has: > ttyv8 "/usr/local/bin/kdm -nodeamon" xterm on secure > Of course I can comment it out, then the errors don't pop up, but that not > what I want > > How can I solve this? Look at the log messages from kdm (and X itself). You're looking for reasons why they (one of them, at least) exit quickly.