On Mon, Feb 4, 2019 at 10:09 PM John O'Meara wrote:
> On Sat, Feb 2, 2019, 4:40 PM Steve Litt wrote:
>> On Sat, 2 Feb 2019 21:08:10 + Colin Booth wrote:
>>> s6-svstat -p /path/to/service | xargs kill SIGNAL
>>
>> Cool. That's all that's needed.
>
> Be careful, though. If the service is
On Sun, Jan 27, 2019 at 1:56 PM Sean MacLennan wrote:
> So it seems that s6-log does not like buffered output. I modified
> doorknob to vsnprintf into a buffer and then tried various output
> methods.
s6-log (or another program) has no idea about your buffered output.
Output cannot be read until
On Thu, Sep 1, 2016 at 8:34 AM, Laurent Bercot
wrote:
> OK, now let's have a look at LISTEN_FDS.
I also find these particular implementation details a poor choice. I
was going to recommend a different environment convention, but then I
saw the pre-existing
On Wed, May 18, 2016 at 11:32 PM, Colin Booth wrote:
> reload.sh:
> #!/bin/sh
> /usr/sbin/haproxy \
> -f /etc/haproxy/haproxy.cfg \
> -f /opt/haproxy-config/combined.cfg \
> -p /tmp/haproxy.pid \
> -sf $(sv s /opt/zsv/jboss/haproxy | awk '{print
>