From owner-freebsd-rc@FreeBSD.ORG Sat Jul 23 15:13:36 2005 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 150AD16A41F for ; Sat, 23 Jul 2005 15:13:36 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBB2543D49 for ; Sat, 23 Jul 2005 15:13:35 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.101] (adsl-68-93-60-6.dsl.rcsntx.swbell.net [68.93.60.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 77F8D3FC38 for ; Sat, 23 Jul 2005 10:13:30 -0500 (CDT) Date: Sat, 23 Jul 2005 10:13:10 -0500 From: Paul Schmehl To: freebsd-rc@freebsd.org Message-ID: In-Reply-To: <20050723122634.GA1024@rogue.smit.lan> References: <468B58E789145A1C6885EA66@utd59514.utdallas.edu> <20050721230123. GA19090@odin.ac.hmc.edu> <20050723122634.GA1024@rogue.smit.lan> X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: New port startup script fails X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jul 2005 15:13:36 -0000 --On July 23, 2005 3:26:35 PM +0300 Mike Makonnen wrote: > On Thu, Jul 21, 2005 at 06:10:45PM -0500, Paul Schmehl wrote: >> >> I'm not sure I understand what you mean here. However, there *is* one >> oddity. When the program is running, ps shows the command to be >> "tclsh8.4 /usr/local/bin/sguil-server/sguild -D -c >> /usr/local/etc/sguil-server/sguild.conf". >> >> Maybe that's the problem? (I thought, since the pidfile was known that >> it wouldn't matter.) >> > > If the command you're starting up is a shell script then you need to set > command_interpreter=yes in your script. In such a case rc.subr(8) will > read the first line of $command and figure out what the interpreter is > and modify the ps(1) string to look for appropriately. And yes, you need > to define $pidfile as well. > I tried using command_interpreter=yes, but I got errors: can't find tclsh8.4 and when I tried adding the full patch, I got errors about ELF?? Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/