❦ 24 octobre 2013 15:25 CEST, Louis Bouchard :
>> Other solutions would be to provide Upstart/systemd scripts or to
>> modify stud to wait for its children before terminating. I can do a
>> patch for the later.
>>
>
> As expressed in my previous comment, here is a patch for stud that will
> hand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour Vincent,
Le 12/10/2013 10:07, Vincent Bernat a écrit :
> Other solutions would be to provide Upstart/systemd scripts or to
> modify stud to wait for its children before terminating. I can do a
> patch for the later.
>
As expressed in my prev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Le 12/10/2013 10:07, Vincent Bernat a écrit :
>
> OK, sorry, I didn't understand that the first time. Since the other
> way to kill stud does not play nice with the multiple instance
> feature, what about put a "sleep 1" between stop and start
❦ 12 octobre 2013 09:15 CEST, Louis Bouchard :
>> It has been some time since I run stud. I just tried and I notice
>> that I have a parent process that is supervising childrens and
>> restarting them when they die. And the PID registered works as
>> expected:
>>
>> ├─stud(3933)─┬─stud(3950) │
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Le 11/10/2013 22:55, Vincent Bernat a écrit :
>
> It has been some time since I run stud. I just tried and I notice
> that I have a parent process that is supervising childrens and
> restarting them when they die. And the PID registered works
❦ 10 octobre 2013 12:01 CEST, Louis Bouchard :
>>> If by multiple instances you mean many configuration files in
>>> /etc/stud I haven't tested. If you mean multiple children (or
>>> cores) started by the -n option, this is indeed what it is trying
>>> to fix.
>>
>> Yes, I mean multiple configur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Le 09/10/2013 17:48, Vincent Bernat a écrit :
>> If by multiple instances you mean many configuration files in
>> /etc/stud I haven't tested. If you mean multiple children (or
>> cores) started by the -n option, this is indeed what it is tryin
❦ 9 octobre 2013 11:11 CEST, Louis Bouchard :
>> How does this work for multiple stud instances? I didn't know that
>> start-stop-daemon does not wait for the process to terminate by
>> default. Maybe we should use --retry instead.
>>
>
> If by multiple instances you mean many configuration fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
Le 09/10/2013 08:47, Vincent Bernat a écrit :
>
> How does this work for multiple stud instances? I didn't know that
> start-stop-daemon does not wait for the process to terminate by
> default. Maybe we should use --retry instead.
>
If b
❦ 8 octobre 2013 15:40 CEST, Louis Bouchard :
> This bug report follows a previously reported bug on Ubuntu :
> https://bugs.launchpad.net/bugs/1123950
>
> Utilization of invoke-rc.d stud restart is failing to restart
> the stud daemon correctly.
>
> This is caused by the use of --pidfile tha
10 matches
Mail list logo
