Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Jul 2005 10:13:10 -0500
From:      Paul Schmehl <pauls@utdallas.edu>
To:        freebsd-rc@freebsd.org
Subject:   Re: New port startup script fails
Message-ID:  <BCA46C33312EB048321BFDD8@Paul-Schmehls-Computer.local>
In-Reply-To: <20050723122634.GA1024@rogue.smit.lan>
References:  <468B58E789145A1C6885EA66@utd59514.utdallas.edu> <20050721230123.	GA19090@odin.ac.hmc.edu> <B858D08121B1B491F0217584@utd59514.utdallas.edu> <20050723122634.GA1024@rogue.smit.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
--On July 23, 2005 3:26:35 PM +0300 Mike Makonnen <mtm@identd.net> 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/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BCA46C33312EB048321BFDD8>