rc.d script for processes started with /usr/bin/env

2006-12-14 Thread Ashley Moran
Hi I just wrote a little ruby web server for internal use. I wrote it on my mac to deploy on FreeBSD, so I used #!/usr/bin/env ruby as the shebang. But when I do that, I can't stop the server with my rc.d script (below). If I change them both to /usr/local/bin/ruby I can make it work.

Re: rc.d script for processes started with /usr/bin/env

2006-12-14 Thread [LoN]Kamikaze
Ashley Moran wrote: Hi I just wrote a little ruby web server for internal use. I wrote it on my mac to deploy on FreeBSD, so I used #!/usr/bin/env ruby as the shebang. But when I do that, I can't stop the server with my rc.d script (below). If I change them both to /usr/local/bin/ruby I

Re: rc.d script for processes started with /usr/bin/env

2006-12-14 Thread Ashley Moran
On 14 Dec 2006, at 12:08, [LoN]Kamikaze wrote: All you need to do is to set command_interpreter=/usr/bin/env for more information have a look at rc.subr(8). Hmm I've just tried that and all I get is... [EMAIL PROTECTED] ~]# /usr/local/etc/rc.d/prolite_password_server stop

Re: rc.d script for processes started with /usr/bin/env

2006-12-14 Thread [LoN]Kamikaze
Ashley Moran wrote: Hmm I've just tried that and all I get is... [EMAIL PROTECTED] ~]# /usr/local/etc/rc.d/prolite_password_server stop prolite_password_server not running? (check /var/run/prolite_password_server/prolite_password_server.pid). Are you certain that this is the pidfile used by

Re: rc.d script for processes started with /usr/bin/env

2006-12-14 Thread Ashley Moran
On 14 Dec 2006, at 13:49, [LoN]Kamikaze wrote: Are you certain that this is the pidfile used by your server? Are you aware that the service is responsible for creating the pidfile, not rc.subr? Yes, on both counts. Works fine with #!/usr/local/bin/ruby and

Re: rc.d script for processes started with /usr/bin/env

2006-12-14 Thread [LoN]Kamikaze
Ashley Moran wrote: On 14 Dec 2006, at 13:49, [LoN]Kamikaze wrote: Are you certain that this is the pidfile used by your server? Are you aware that the service is responsible for creating the pidfile, not rc.subr? Yes, on both counts. Works fine with #!/usr/local/bin/ruby and