On Wed, 29 Aug 2012 23:06:45 -0400
Steve Wills mentioned:
> On 08/29/12 21:38, Doug Barton wrote:
> >
> > I'm pretty sure you actually want to use command_interpreter instead of
> > procname. It should actually be very rare to use procname directly in an
> > rc.d script.
>
> Got it, although th
On 08/29/12 21:38, Doug Barton wrote:
>
> I'm pretty sure you actually want to use command_interpreter instead of
> procname. It should actually be very rare to use procname directly in an
> rc.d script.
Got it, although that means picking the value at build time, but that
seems OK.
> That said,
On 08/29/2012 09:28 AM, Steve Wills wrote:
> Hi,
>
> I've encountered a situation with an rc script that I'm not sure how to
> solve. The issue is summarized well in this PR:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/170980
>
> Basically, the "ruby" that's in use can vary because ruby
On 08/29/12 18:33, David O'Brien wrote:
> On Wed, Aug 29, 2012 at 03:57:33PM -0400, Steve Wills wrote:
>> name="mcollectived"
>> command="%%PREFIX%%/sbin/${name}"
>> read procname <"${command}"
>> procname="%%PREFIX%%/bin/${procname##*/}"
>
> Wouldn't this work?
>
> name="mcollectived"
> command=
On Wed, Aug 29, 2012 at 03:57:33PM -0400, Steve Wills wrote:
> name="mcollectived"
> command="%%PREFIX%%/sbin/${name}"
> read procname <"${command}"
> procname="%%PREFIX%%/bin/${procname##*/}"
Wouldn't this work?
name="mcollectived"
command="%%PREFIX%%/sbin/${name}"
procname="%%PREFIX%%/bin/${com
On 08/29/12 15:39, Steve Wills wrote:
> On 08/29/12 15:28, Steve Wills wrote:
>> Hi,
>>
>> I've encountered a situation with an rc script that I'm not sure how to
>> solve. The issue is summarized well in this PR:
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/170980
>>
>> Basically, the "r
On 08/29/12 15:28, Steve Wills wrote:
> Hi,
>
> I've encountered a situation with an rc script that I'm not sure how to
> solve. The issue is summarized well in this PR:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/170980
>
> Basically, the "ruby" that's in use can vary because ruby 1.8
Hi,
I've encountered a situation with an rc script that I'm not sure how to
solve. The issue is summarized well in this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/170980
Basically, the "ruby" that's in use can vary because ruby 1.8 or ruby
1.9 may be used. There may be "ruby", "ruby18"