I found a simple workaround by using the unbuffer utility, which uses a
pseudo terminal to get the desired line-buffering-only behavior.
$ unbuffer lxc-monitor -n container-1 > output
Ken
On Fri, Sep 7, 2012 at 5:25 PM, Ken Elkabany <k...@elkabany.com> wrote:
> On Thu, Sep 6, 2012 at 11:13 PM, Fajar A. Nugraha <l...@fajar.net> wrote:
>
>> On Fri, Sep 7, 2012 at 7:46 AM, Ken Elkabany <k...@elkabany.com> wrote:
>> > 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?
>>
>> (optional: start a screen session)
>> $ script -f /path/to/your-logfile.txt
>> $ lxc-monitor -n container-1
>>
>> ... and on other terminal
>> $ tail -f /path/to/your-logfile.txt
>>
>> --
>> Fajar
>>
>
> Unfortunately, in my application there won't be any open terminals. I
> simply used that as an example to illustrate my point.
>
> 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
