Christos Trochalakis wrote:
On Sat, Jun 27, 2015 at 03:05:01AM +, Eric Wong wrote:
>Is it possible to make systemd fire up two unicorn masters?
>That would be a nice feature to have with socket activation.
That would be great! I am a bit surprised that specifying multiple
se
On Sat, Jun 27, 2015 at 03:05:01AM +, Eric Wong wrote:
Christos Trochalakis wrote:
On Thu, Jun 25, 2015 at 11:26:26PM +, Eric Wong wrote:
>With socket activation, you should just be able to kill unicorn using
>SIGQUIT (just master, or even all workers) and restart withou
On Sat, Jun 27, 2015 at 04:01:36AM +, Eric Wong wrote:
Unfortunately, testing this is tricky because FD=3
(SD_LISTEN_FDS_START) tends to be grabbed by (MRI) Ruby 1.9.3
and onwards for the internal self-pipe.
So for now, I've manually tested this with a systemd installation
Disclaimer: this
Hello all,
I have recently migrated our main ruby application to systemd implementing zero
downtime upgrades.
systemd doesn't like replacing the binary on the fly. There is one exception to
this, services with PIDFile. When PIDFile is set, systemd reads it when the
main process exits and replace
On Thu, Jun 25, 2015 at 11:26:26PM +, Eric Wong wrote:
+Cc unicorn-public list
Christos Trochalakis wrote:
Hello all,
I have recently migrated our main ruby application to systemd implementing zero
downtime upgrades.
systemd doesn't like replacing the binary on the fly. There i
pn ruby-dev
ii rubygems-integration 1.4
ii sudo 1.8.9p4-1
bundler suggests no packages.
-- no debconf information
>From 1a223186cda873de5782769f2cf6b0a1bc314426 Mon Sep 17 00:00:00 2001
From: Christos Trochalakis
Date: Sun, 9 Feb 2014 10:44:31 +0200
Subject: [P
