Re: cvs commit: ports/net/haproxy-devel/files haproxy.in

2012-06-05 Thread Doug Barton
On 6/5/2012 10:46 AM, Dmitry Sivachenko wrote: > On 6/5/12 9:11 PM, Doug Barton wrote: >> The way that's properly written for rc.d would be to replace the 2 lines >> with this one line: >> >> err 1 "No process found. Maybe $command isn't running?" >> >> Other notes, >> >> 1. The files need a $Free

Re: cvs commit: ports/net/haproxy-devel/files haproxy.in

2012-06-05 Thread Dmitry Sivachenko
On 6/5/12 9:11 PM, Doug Barton wrote: The way that's properly written for rc.d would be to replace the 2 lines with this one line: err 1 "No process found. Maybe $command isn't running?" Other notes, 1. The files need a $FreeBSD$ 2. REQUIRE: LOGIN is a better choice, but if there is a reason

Re: cvs commit: ports/net/haproxy-devel/files haproxy.in

2012-06-05 Thread Doug Barton
The way that's properly written for rc.d would be to replace the 2 lines with this one line: err 1 "No process found. Maybe $command isn't running?" Other notes, 1. The files need a $FreeBSD$ 2. REQUIRE: LOGIN is a better choice, but if there is a reason for them to run earlier, that's Ok. Tha

Re: cvs commit: ports/net/haproxy-devel/files haproxy.in haproxy.sh.in

2007-08-05 Thread Doug Barton
Marcelo Araujo wrote: > araujo 2007-08-05 20:14:02 UTC > > FreeBSD ports repository > > Added files: > net/haproxy-devel/files haproxy.in > Removed files: > net/haproxy-devel/files haproxy.sh.in > Log: > - Forgot the new RC script by last commit! > > PR: