Hi Jacob,
On Wed, Jun 08, 2011 at 08:47:15PM -0400, Jacob Fenwick wrote:
> Willy,
>
> Thanks for your quick response.
>
> I did some experimenting and realized you were right.
> I think my issue why I couldn't run it as anything but root was because I
> was using the -p option to store the pid i
Willy,
Thanks for your quick response.
I did some experimenting and realized you were right.
I think my issue why I couldn't run it as anything but root was because I
was using the -p option to store the pid in /var/run/haproxy.pid, which
could only accessed by root.
However, I am still having s
On Thu, Jun 09, 2011 at 12:07:27AM +0200, Graeme Donaldson wrote:
> On 9 June 2011 00:05, Jacob Fenwick wrote:
>
> > It seems like I must be root to start haproxy.
> >
> > I know that I can add a user line in global so that the process will change
> > to say it is running as a non-root user once
That's fine, I don't need any ports <1024.
If anyone knows of a solution let me know but I'm guessing it is unlikely.
On Wed, Jun 8, 2011 at 6:07 PM, Graeme Donaldson wrote:
> On 9 June 2011 00:05, Jacob Fenwick wrote:
>
>> It seems like I must be root to start haproxy.
>>
>> I know that I can
On 9 June 2011 00:05, Jacob Fenwick wrote:
> It seems like I must be root to start haproxy.
>
> I know that I can add a user line in global so that the process will change
> to say it is running as a non-root user once it is running, but it seems
> like I still need to be root to actually start i
It seems like I must be root to start haproxy.
I know that I can add a user line in global so that the process will change
to say it is running as a non-root user once it is running, but it seems
like I still need to be root to actually start it, or restart it.
Is there any way around this?
Jaco
6 matches
Mail list logo
