From owner-freebsd-current@FreeBSD.ORG Tue Jul 5 10:20:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0BAC16A41C for ; Tue, 5 Jul 2005 10:20:14 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AEDF43D46 for ; Tue, 5 Jul 2005 10:20:14 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from beatrix.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j65AKB0M015981; Tue, 5 Jul 2005 13:20:12 +0300 Received: from beatrix.daedalusnetworks.priv (localhost [127.0.0.1]) by beatrix.daedalusnetworks.priv (8.13.3+Sun/8.13.3) with ESMTP id j65AKBJL005670; Tue, 5 Jul 2005 13:20:11 +0300 (EEST) Received: (from keramida@localhost) by beatrix.daedalusnetworks.priv (8.13.3+Sun/8.13.3/Submit) id j65AKAw9005669; Tue, 5 Jul 2005 13:20:10 +0300 (EEST) X-Authentication-Warning: beatrix.daedalusnetworks.priv: keramida set sender to keramida@freebsd.org using -f Date: Tue, 5 Jul 2005 13:20:10 +0300 From: Giorgos Keramidas To: Marcin Jessa Message-ID: <20050705102010.GA5663@beatrix.daedalusnetworks.priv> References: <20050705115234.44adc0ed.lists@yazzy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050705115234.44adc0ed.lists@yazzy.org> Cc: freebsd-current@freebsd.org Subject: Re: getty replacement X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2005 10:20:14 -0000 On 2005-07-05 11:52, Marcin Jessa wrote: > Hi guys. > > Is there any way to replace "/usr/libexec/getty Pc" with a custom > application and what would be requirements for such an app? > Running > ttyv0 "/some/app/shell_code.sh Pc" cons23 on secure > gives me: > init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 secs > and my code is not executed. Your shell script exits immediately, which leads init to believe something caused it to exit prematurely. Shell scripts that don't exit, but continue working until they are explicitly terminated with a signal should work fine.