[lxc-devel] lxc_monitord - monitor exiting

[Serge Hallyn]

Quoting S.Çağlar Onur (caglar at 10ur.org):
> Hey Dwight,
> 
> I'm observing following behavior with staging tree and just wanted to make
> sure that what I'm seeing is the expected;
> 
> * Initially nothing runs
> 
> [caglar at qgq:~/Projects/lxc/examples] sudo ./list
> bankai (STOPPED)
> bleach (STOPPED)
> zangetsu (STOPPED)
> 
> * I start one container using the API
> 
> [caglar at qgq:~/Projects/lxc/examples] sudo ./start -name zangetsu
> Starting the container...
> 
> [caglar at qgq:~/Projects/lxc/examples] sudo ./list
> bankai (STOPPED)
> bleach (STOPPED)
> zangetsu (RUNNING)
> 
> * monitord starts as expected but exits after 30 seconds later (although
> container is still running);
> 
> [caglar at qgq:~/Projects/lxc-upstream(staging)] tail -f
> /var/lib/lxc/lxc-monitord.log
>    lxc-monitord 1367004858.616 NOTICE   lxc_monitord - monitoring lxcpath
> /var/lib/lxc
>    lxc-monitord 1367004888.677 NOTICE   lxc_monitord - no clients for 30
> seconds, exiting
>    lxc-monitord 1367004888.677 NOTICE   lxc_monitord - monitor exiting
> 
> [caglar at qgq:~/Projects/lxc/examples] sudo ./list
> bankai (STOPPED)
> bleach (STOPPED)
> zangetsu (RUNNING)
> 
> [caglar at qgq:~/Projects/lxc/examples] ps aux | grep monitord
> caglar   28404  0.0  0.0   7240   624 pts/54   S+   15:34   0:00 tail -f
> /var/lib/lxc/lxc-monitord.log
> caglar   29037  0.0  0.0   9436   948 pts/0    S+   15:38   0:00 grep
> --color=auto monitord
> [caglar at qgq:~/Projects/lxc/examples]
> 
> I'm asking cause I was under the impression that lxc-monitord will keep
> running as long as there is a container. Am I wrong?

That was our original design, yes.  If you want to be watching container
state changes, then you should simply run lxc-monitor.

Does that complicate something for you?

-serge