Hi Tim, On Fri, Apr 26, 2019 at 12:15:37AM +0200, Tim Duesterhus wrote: > [Service] > -Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid" > +Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid" > "MASTER_SOCKET=/run/haproxy-master.sock" > ExecStartPre=@SBINDIR@/haproxy -f $CONFIG -c -q > -ExecStart=@SBINDIR@/haproxy -Ws -f $CONFIG -p $PIDFILE > +ExecStart=@SBINDIR@/haproxy -Ws -S $MASTER_SOCKET -f $CONFIG -p $PIDFILE > ExecReload=@SBINDIR@/haproxy -f $CONFIG -c -q
In my opinion that's not a good idea to do it this way, because you can't disable the master CLI by unsetting the MASTER_SOCKET variable. It's probably better to have "-S /run/haproxy-master.sock" in an $OPTIONS variable at the end of the ExecStart line. -- William Lallemand
