On Tue, Aug 28, 2012 at 2:07 PM, Dan Kegel <d...@kegel.com> wrote: > Well, that was anticlimactic. Here's the script, for what it's worth.
But wait, there's more. This script tries to clean up after itself when you kill it, and it fails miserably. And after some investigation, it turns out that lxc-start-ephemeral also fails miserably if you send it a SIGINT. Although it does catch SIGINT and do the right thing, it won't get the SIGINT until lxc-start ends, and that won't end until lxc-wait ends, and that won't happen until... somebody stops the ephemeral machine, which presumably was the whole reason the SIGINT was sent in the first place. So, maybe the 'lxc-stop' in lxc-start-ephemeral's cleanup routine is moot! So much for signals as an exposed interface. I'm going to revisit my script now and rewrite it to provide a nicer, working, way to stop the nested machine and the loop. - Dan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
