On Mon, 30 Sep 2013 10:29:50 -0400 Stéphane Graber <stgra...@ubuntu.com> wrote:
> On Mon, Sep 30, 2013 at 09:53:56AM -0400, Dwight Engen wrote: > > On Fri, 27 Sep 2013 21:01:07 -0500 > > Serge Hallyn <serge.hal...@ubuntu.com> wrote: > > > > > This is an api function which will return false if the container > > > is running, and the caller may not talk to its monitor over its > > > command socket. Otherwise - if the container is not running, or > > > the caller may access it - it returns true. > > > > > > We can use this in several tools early on to prevent the segvs > > > etc which we currently get. > > > > > > Signed-off-by: Serge Hallyn <serge.hal...@ubuntu.com> > > > > Acked-by: Dwight Engen <dwight.en...@oracle.com> > > Hi Serge, > > So I'm not terribly familiar with the control code since the monitord > changes, will that code work properly if the container socket is > already in use (say by someone running lxc-wait on the container)? Hi Stéphane, A big part of that change was to support multiple, concurrent lxc-wait and lxc-monitor clients which I did test at the time, so I'm glad to hear from Serge that it is still working :) ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
