From owner-freebsd-current@FreeBSD.ORG Tue Jul 5 10:44:56 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 0D6DD16A41C; Tue, 5 Jul 2005 10:44:56 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC5E243D45; Tue, 5 Jul 2005 10:44:55 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=h311r4z3r) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1Dpkv6-0005o2-3T; Tue, 05 Jul 2005 12:44:53 +0200 Date: Tue, 5 Jul 2005 12:45:01 +0200 From: Marcin Jessa To: Giorgos Keramidas Message-Id: <20050705124501.6c9de799.lists@yazzy.org> In-Reply-To: <20050705102010.GA5663@beatrix.daedalusnetworks.priv> References: <20050705115234.44adc0ed.lists@yazzy.org> <20050705102010.GA5663@beatrix.daedalusnetworks.priv> Organization: YazzY.org X-Mailer: Sylpheed version 1.9.12 (GTK+ 2.6.8; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.5 (--) 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:44:56 -0000 On Tue, 5 Jul 2005 13:20:10 +0300 Giorgos Keramidas wrote: > 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. That unfortunatelly does not seem to work. I tried a shell script with a read -p "Blah blah" my_choice which should wait for an execution but this did not work either giving me exactly the same message...