Christos Trochalakis yati...@ideopolis.gr 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
Christos Trochalakis yati...@ideopolis.gr wrote:
On Sat, Jun 27, 2015 at 03:05:01AM +, Eric Wong wrote:
Christos Trochalakis yati...@ideopolis.gr wrote:
KillMode=mixed
I don't think KillMode=mixed is necessary, here. systemd can send
SIGQUIT to workers.
Perhaps there is a race
On Sat, Jun 27, 2015 at 03:05:01AM +, Eric Wong wrote:
Christos Trochalakis yati...@ideopolis.gr 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
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
Christos Trochalakis yati...@ideopolis.gr 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 without ever
dropping a connection. I do NOT suggest using
+Cc unicorn-public list
Christos Trochalakis chris...@skroutz.gr 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 is one exception
to
this, services with
Dmitry Smirnov only...@debian.org wrote:
On Wed, 24 Jun 2015 23:26:49 Eric Wong wrote:
Dmitry: unicorn upstream here, is there anything in unicorn itself
can do to make systemd integration easier?
Thank you very much for keeping an eye on us and for all your help.
I'm not sure if we need
On Thu, Jun 25, 2015 at 11:26:26PM +, Eric Wong wrote:
+Cc unicorn-public list
Christos Trochalakis chris...@skroutz.gr 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
On Fri, 26 Jun 2015 00:34:36 Hleb Valoshka wrote:
So if it still supports sysv scripts and native services does not
provide additional functions why to add useless native support which
breaks enhanced sysv features?
Because native support works better than SysV emulation. Because supporting
On 6/25/15, Dmitry Smirnov only...@debian.org wrote:
Not sure... I know systemd can invoke init.d script but only standard
{start|
stop|restart|status} functions and only with the absence of native .service
file.
So if it still supports sysv scripts and native services does not
provide
Hi Christos,
On Thu, 25 Jun 2015 11:50:57 Christos Trochalakis wrote:
I have recently migrated our main ruby application to systemd implementing
zero downtime upgrades.
[...]
Thank you for a very useful hints. I'll update .service file as soon as I try
soft restart under systemd.
On more
Hi Eric,
On Wed, 24 Jun 2015 23:26:49 Eric Wong wrote:
Dmitry: unicorn upstream here, is there anything in unicorn itself
can do to make systemd integration easier?
Thank you very much for keeping an eye on us and for all your help.
I'm not sure if we need anything special -- let me experiment
Adding unicorn-pub...@bogomips.org to Cc:
Those of you who haven't followed along on the unic...@packages.debian.org
list can catch up here:
http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2015-June/024539.html
Dmitry: unicorn upstream here, is there anything in unicorn
On Wed, 24 Jun 2015 12:02:46 Hleb Valoshka wrote:
On 6/23/15, Dmitry Smirnov only...@debian.org wrote:
It seems that --update-rcd-params=disable (or remove) is the solution.
I tried that but it does not work and produces error on installation of
the package...
I'll test it too when I
On 6/22/15, Dmitry Smirnov only...@debian.org wrote:
Perhaps it might be better to make sure that daemon is not enabled after
first install of the package?
It sounds reasonably.
I realised that dh_installinit --no-start still enables automatic start
of
daemon so I've added workaround to
On Mon, 22 Jun 2015 19:45:23 Hleb Valoshka wrote:
It seems that --update-rcd-params=disable (or remove) is the solution.
I tried that but it does not work and produces error on installation of the
package...
I don't want to lose transparent upgrade feature and it's not possible
with default
On 6/19/15, Dmitry Smirnov only...@debian.org wrote:
I took liberty to commit native systemd service to unicorn repository.
Thanks! I hope it works properly (I can't test as I'm not a systemd
user). But I have several comments regarding your changes:
* You have removed CONFIGURED variable,
On Sun, 21 Jun 2015 18:19:44 Hleb Valoshka wrote:
I hope it works properly (I can't test as I'm not a systemd
user).
I've been using unicorn.service for some weeks and it works for me although my
local .service file also creates directory for .sock file and set permissions
on it...
But I
Dear Hleb,
Thank you for maintaining unicorn in Debian.
I took liberty to commit native systemd service to unicorn repository.
I shall be happy to answer all your questions and hopefully help little more
with Unicorn maintenance, if time allows.
Please let me know what you think.
--
Regards,
19 matches
Mail list logo
