<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText>Ah, I wasn't aware of the startup/shutdown hook scripts either, that'll be a perfect place to add/remove the symbolic link in <span style='font-family:"Courier New"'>/etc/lxc/auto</span><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Do you know if <span style='font-family:"Courier New"'>lxc.hook.post-stop</span> is run even if you power off from within the container with <span style='font-family:"Courier New"'>shutdown -P now</span>?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Also, can I define multiple post-stop hooks? For example, if I wanted to run 2 commands but didn’t want to distribute a custom script to all my hosts? The Ubuntu docs don’t call that point out specifically.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Thanks much,<o:p></o:p></p><p class=MsoPlainText>David<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: Jäkel, Guido [mailto:G.Jaekel@dnb.de] <br>Sent: Monday, May 06, 2013 8:44 PM<br>To: David Parks; 'lxc-users@lists.sourceforge.net'<br>Cc: Ha Ho<br>Subject: RE: [Spam-Wahrscheinlichkeit=87][Lxc-users] Restarting LXC containers after power failure</p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Dear David,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>this will require to persist the current "power state" of a container by some kind of marker. A tricky way is to mark some container-related file, e.g. to ("miss"-) use the sticky bit of the containers lxc configuration file or to put some marker file into the containers rootfs.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>This will allow to write an init script that will scan for such a marker and (re)start the corresponding container. Using LXC's startup/shutdown hook scripts, you may event set such a marker automagical and especially to remove it on a regular shutdown. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>>-----Original Message-----<o:p></o:p></p><p class=MsoPlainText>>From: David Parks [<a href="mailto:david.parks@frugg.com"><span style='color:windowtext;text-decoration:none'>mailto:david.parks@frugg.com</span></a>]<o:p></o:p></p><p class=MsoPlainText>>Sent: Monday, May 06, 2013 2:59 PM<o:p></o:p></p><p class=MsoPlainText>>To: <a href="mailto:lxc-users@lists.sourceforge.net"><span style='color:windowtext;text-decoration:none'>lxc-users@lists.sourceforge.net</span></a><o:p></o:p></p><p class=MsoPlainText>>Cc: Ha Ho<o:p></o:p></p><p class=MsoPlainText>>Subject: [Spam-Wahrscheinlichkeit=87][Lxc-users] Restarting LXC <o:p></o:p></p><p class=MsoPlainText>>containers after power failure<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>>We just had a datacenter power failure, upon restart of course our LXC <o:p></o:p></p><p class=MsoPlainText>>containers were stopped. It would be just dandy if there were an LXC option to restart the containers that were already running before the sudden failure.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>>Is there any such capability?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p></div></body></html>