[Libguestfs] OpenStack output workflow
Fabien Dupont
fdupont at redhat.com
Thu Oct 4 14:08:48 UTC 2018
New code tries SIGTERM first, with a grace period of 30 seconds:
https://github.com/ManageIQ/manageiq-content/pull/433.
On Wed, Sep 26, 2018 at 6:10 PM Richard W.M. Jones <rjones at redhat.com>
wrote:
> On Wed, Sep 26, 2018 at 04:57:19PM +0200, Fabien Dupont wrote:
> > It's not virt-v2v-wrapper that kills virt-v2v, it's ManageIQ. We have the
> > PID from virt-v2v-wrapper state file. What would be the preferred way
> > to interrupt it ?
>
> It's not too nice to send kill -9 to virt-v2v because it means none of
> the at-exit handlers get to run, so it will leave temporary files all
> over the place. It's better to send an ordinary kill signal
> (eg. SIGTERM). If virt-v2v doesn't exit after some grace period,
> eg. 30 seconds, then it's a bug, but maybe you could then send
> SIGKILL.
>
> This is actually another thing which a temporary systemd unit will
> solve for us:
> https://www.freedesktop.org/software/systemd/man/systemd.kill.html
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-top is 'top' for virtual machines. Tiny program with many
> powerful monitoring features, net stats, disk stats, logging, etc.
> http://people.redhat.com/~rjones/virt-top
>
--
*Fabien Dupont*
PRINCIPAL SOFTWARE ENGINEER
Red Hat - Solutions Engineering
fabien at redhat.com M: +33 (0) 662 784 971 <+33662784971>
<http://redhat.com> *TRIED. TESTED. TRUSTED.*
Twitter: @redhatway <https://twitter.com/redhatway> | Instagram: @redhatinc
<https://www.instagram.com/redhatinc/> | Snapchat: @redhatsnaps
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libguestfs/attachments/20181004/ffa11a0c/attachment.htm>
More information about the Libguestfs
mailing list