From owner-freebsd-questions@FreeBSD.ORG Wed Jan 5 12:12:41 2011 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 710671065697 for ; Wed, 5 Jan 2011 12:12:41 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2AD7F8FC25 for ; Wed, 5 Jan 2011 12:12:40 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirg.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1PaSEJ-00024b-Oz; Wed, 05 Jan 2011 12:12:39 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1PaSEJ-0000Da-Ij; Wed, 05 Jan 2011 12:12:39 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4) with ESMTP id p05CCdjj038541; Wed, 5 Jan 2011 12:12:39 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4/Submit) id p05CCdnF038540; Wed, 5 Jan 2011 12:12:39 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Wed, 5 Jan 2011 12:12:39 +0000 From: Anton Shterenlikht To: Matthew Seaman Message-ID: <20110105121239.GB38449@mech-cluster241.men.bris.ac.uk> Mail-Followup-To: Matthew Seaman , freebsd-questions@freebsd.org References: <20101227141122.GA1741@mech-cluster241.men.bris.ac.uk> <4D18AB0C.50707@infracaninophile.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D18AB0C.50707@infracaninophile.co.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-questions@freebsd.org Subject: Re: init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs 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: Wed, 05 Jan 2011 12:12:41 -0000 On Mon, Dec 27, 2010 at 03:04:44PM +0000, Matthew Seaman wrote: > On 27/12/2010 14:11, Anton Shterenlikht wrote: > > On 9.0-CURRENT r216732 ia64 I get this message: > > > > % grep getty /var/log/messages | tail > > Dec 27 13:26:57 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:27:27 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:27:57 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:45:22 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:45:53 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:46:23 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:52:55 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:53:25 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:57:56 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > Dec 27 13:58:26 mech-cluster241 init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 secs > > % > > > > % grep ttyv8 /etc/ttys > > ttyv8 "/usr/local/bin/xdm" xterm on secure > > > > % cat /var/log/xdm.log > > % > > > > And no other indication of anything going wrong. > > > > I've seen quite a few similar reports on the net, > > but no conclusive answer. > > > > What exactly does the above message mean? > > Usually that xdm is failing to start. getty will keep trying to run it, > and wil fill your log files with messages of failure until you fix the > problem. > > I'd turn off xdm on that vty temporarily, [change 'on' to 'off' in that > line in /etc/ttys, and 'kill -HUP 1' to restart init] and then try > running xdm manually from the console to see what happens. It could be > all sorts of things causing the problem. Matthew, yes, this helped. I don't get this message in the logs anymore. Perhaps the problem is that this node has no graphics card. It accepts XDMCP connections only via network. All virtual terminals are off, only serial terminals are allowed in /etc/ttys. Maybe this conficts with the normal operation of getty.. I'd still like to start xdm automatically on reboot. If I can't do it via /etc/ttys, what would be the alternative way? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423