Not sure, but I guess since nginx process is a child process of kimchid process, in theory, when kimchid process is finished (or 'gracefully' killed) all child process should finish with no problems.<br><br><div class="gmail_quote">On Tue Jan 27 2015 at 8:00:50 AM Royce Lv <<a href="mailto:lvroyce@linux.vnet.ibm.com">lvroyce@linux.vnet.ibm.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 01/26/2015 02:38 PM, Aline Manera wrote:<br>
><br>
> On 26/01/2015 16:48, Rodrigo Trujillo wrote:<br>
>> Kimchi has a problem when updating itself. Kimchid is restarted and all<br>
>> children are killed, including Yum. When that happens, the updates are<br>
>> not finished properly and the system ends up in an inconsistent state.<br>
>> This patch changes the Systemd KillMode to "process", so, child<br>
>> processes will remain in the system, letting yum finishes all<br>
>> transactions in background, while kimchi restarts correctly.<br>
><br>
> Probably we have the same behaviour for Ubuntu and openSUSE. Have you<br>
> checked them?<br>
><br>
>> Signed-off-by: Rodrigo Trujillo <<a href="mailto:rodrigo.trujillo@linux.vnet.ibm.com" target="_blank">rodrigo.trujillo@linux.vnet.<u></u>ibm.com</a>><br>
>> ---<br>
>> contrib/<a href="http://kimchi.spec.fedora.in" target="_blank">kimchi.spec.fedora.in</a> | 6 ++++--<br>
>> contrib/kimchid.service.fedora | 2 +-<br>
>> 2 files changed, 5 insertions(+), 3 deletions(-)<br>
>><br>
>> diff --git a/contrib/<a href="http://kimchi.spec.fedora.in" target="_blank">kimchi.spec.fedora.<u></u>in</a><br>
>> b/contrib/<a href="http://kimchi.spec.fedora.in" target="_blank">kimchi.spec.fedora.<u></u>in</a><br>
>> index 92d3e49..4236641 100644<br>
>> --- a/contrib/<a href="http://kimchi.spec.fedora.in" target="_blank">kimchi.spec.fedora.<u></u>in</a><br>
>> +++ b/contrib/<a href="http://kimchi.spec.fedora.in" target="_blank">kimchi.spec.fedora.<u></u>in</a><br>
>> @@ -109,10 +109,12 @@ install -Dm 0755 contrib/kimchid.sysvinit<br>
>> %{buildroot}%{_initrddir}/<u></u>kimchid<br>
>> %post<br>
>> if [ $1 -eq 1 ] ; then<br>
>> /bin/systemctl enable kimchid.service >/dev/null 2>&1 || :<br>
>> - # Initial installation<br>
>> - /bin/systemctl daemon-reload >/dev/null 2>&1 || :<br>
>> fi<br>
>><br>
>> +# Reload systemd in initial install and in update, because<br>
>> kimchid.service<br>
>> +# may have been changed<br>
>> +/bin/systemctl daemon-reload >/dev/null 2>&1 || :<br>
>> +<br>
>><br>
>> %preun<br>
>><br>
>> diff --git a/contrib/kimchid.service.<u></u>fedora<br>
>> b/contrib/kimchid.service.<u></u>fedora<br>
>> index 7abe49b..92b8d86 100644<br>
>> --- a/contrib/kimchid.service.<u></u>fedora<br>
>> +++ b/contrib/kimchid.service.<u></u>fedora<br>
>> @@ -6,7 +6,7 @@ After=libvirtd.service<br>
>> [Service]<br>
>> Type=simple<br>
>> ExecStart=/usr/bin/kimchid<br>
>> -ExecStop=/bin/kill -TERM $MAINPID<br>
>> +KillMode=process<br>
We started nginx proxy in kimchi server, will it also be stopped and<br>
restarted correctly?<br>
>> EnvironmentFile=/etc/kimchi/<u></u>kimchi.conf<br>
>><br>
>> [Install]<br>
><br>
> ______________________________<u></u>_________________<br>
> Kimchi-devel mailing list<br>
> <a href="mailto:Kimchi-devel@ovirt.org" target="_blank">Kimchi-devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/kimchi-devel</a><br>
><br>
<br>
______________________________<u></u>_________________<br>
Kimchi-devel mailing list<br>
<a href="mailto:Kimchi-devel@ovirt.org" target="_blank">Kimchi-devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel" target="_blank">http://lists.ovirt.org/<u></u>mailman/listinfo/kimchi-devel</a><br>
</blockquote></div>