On Wed, 2014-03-19 at 18:21 +0100, Robin Monjo wrote: > Hello, > > > I'm using LXC 0.7.5 with the stock ubuntu template. My containers are > running ruby processes that are managed by upstart (launched by > upstart scripts). > > > I need these processes to be gracefully stopped when shutting down a > container, i.e send the SIGTERM signal and wait for it to be done > before fully shutting down my container. > > > I see that inside a container, upstart listen for the SIPWR signal and > execute "shutdown -h now "SIGPWR received"", is it safe to remove this > in order to achieve my goal ? Or is there any other alternatives ?
Ok... So, why not use a SIGPWR? That's the convention. Are you married to using SIGTERM for this purpose? I'm just getting ready to make sure the Fedora and CentOS templates adhere to the SIGPWR convention for both Upstart and Systemd. Why SIGTERM now? And the simple answer to your question is "no, it is not safe - it will cause other timeouts, delays, and problems". > Regards, > Robin Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 978-7061 | [email protected] /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!
signature.asc
Description: This is a digitally signed message part
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
