On 02/02/2011 01:15 AM, Trent W. Buck wrote:
> Daniel Lezcano<[email protected]>  writes:
>
>> On 02/01/2011 12:04 PM, Dean Mao wrote:
>>> Hi,
>>>
>>> I've been messing around with trying to get the output of lxc-start into a
>>> file some.  I know that lxc-start produces a log file, as well as the
>>> ability to fetch the dmesg file directly from the container's log file
>>> directory, but I was curious if it was possible to just run lxc-start in a
>>> nohup and use some kind of dummy getty instance to pipe the output into a
>>> file.  The closest thing I could find was using screen's logging capability.
>>>    The log file produced by lxc-start doesn't really resemble the output
>>> generated from the container boot.  Is there dummy getty/terminal thing that
>>> I could get the actual output of the container boot process?
>> Ok, I just realize I forget to commit the patch to output the console to
>> a file :)
> Uh, lxc-start -s lxc.console=/var/log/lxc/foo.console works for me, as
> at 0.7.3.

Gah ! Right, forget this option too :D


------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Lxc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxc-users

Reply via email to