Hi,
The following outputs container state changes to the terminal as expected:
$ lxc-monitor -n container-1
However, the following outputs the same state changes to a file only after
a certain buffer size has been reached:
$ lxc-monitor -n container-1 &> output
This is problematic because it means that live monitoring cannot be done by
a separate program. The buffering delays messages, potentially indefinitely.
Is there a way around this? Alternatively, is there another way of getting
callbacks or triggers when a container changes state? I was surprised that
lxc-wait was simply a bash script that polled lxc-info every second, which
in my use case is insufficient.
Best,
Ken
------------------------------------------------------------------------------
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
