[Lxc-users] shutting down CentOS6 container

[Derek Simkowiak]

 > /I tried the python script, it just works fine./

     Q1: How does the "kill -INT init" method affect running processes, 
especially MySQL and other databases that may need to shutdown 
gracefully to avoid data corruption?

     I believe that the child processes (incl. mysqld, apache, etc.) 
would be able to shutdown gracefully without data corruption, because 
they'd be killed with a signal that will invoke their internal signal 
handlers.  But, I am looking for independent confirmation.


     Q2: How is lxc-stop -n $CONTAINERNAME different from the Python 
script mentioned below?  Will lxc-stop on a container cause an unclean 
shutdown, or does it also use a Unix signal?


Thanks,
Derek

On 10/17/2011 01:37 PM, Papp Tamas wrote:
> On 10/17/2011 10:26 PM, Milos Negovanovic wrote:
>> If I am not mistaken thats similar approach to using this script:
>>
>> http://pastie.org/2713689
>>
>> Ive tried using that python script, but instead of shutting down my
>> container restarts! Can you paste your container /etc/inittab by any
>> chance?
>>
> There is no inittab, Ubuntu and also CentOS 6 uses upstart.
> I tried the python script, it just works fine.
>
> tamas
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Lxc-users mailing list
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20111017/231bd9c2/attachment.html>