Hi, "Finally, other features we hope to complete by 13.10 (though getting all of them done is unlikely) include cgroup fake roots, a devices namespace, and a system log namespace."
Source: http://s3hh.wordpress.com/2012/05/03/lxc-in-precise-and-beyond/ Regards, Csordás Csaba Ifj. On Mon, Feb 4, 2013 at 10:34 AM, Miroslav Lednicky <miroslav.ledni...@fnusa.cz> wrote: > Dear Guido, > > done. I have syslog without corrupted kernel messages now. > But how can i log kernel messages pre container? Is it possible? > > Best regards, > > Miroslav. > > Dne 24.1.2013 12:55, Jäkel, Guido napsal(a): >> Dear Miroslav, >> >> In case of rsyslog, for every container (but obviously not for the host) >> edit /etc/rsyslog.conf the disable loading of the imklog module by >> "hashing it out": >> >> [...] >> #$ModLoad imklog # provides kernel logging support (previously done >> by rklogd) >> [...] >> >> >> Sincerely >> >> Guido >> >>> -----Original Message----- >>> From: Miroslav Lednicky [mailto:miroslav.ledni...@fnusa.cz] >>> Sent: Thursday, January 24, 2013 11:11 AM >>> To: Jäkel, Guido >>> Cc: 'lxc-users@lists.sourceforge.net' >>> Subject: Re: [Lxc-users] Syslog >>> >>> Dear Guido, >>> >>> I am using rsyslog and distribution Ubuntu. >>> >>> Thank you, >>> >>> Miroslav. >>> >>> Dne 24.1.2013 10:49, Jäkel, Guido napsal(a): >>>> Dear Miroslav, >>>> >>>> please ensure that the syslog deamon within all containers don't log the >>>> kernel logfile source. If you "drain" this source by more than one >>> syslog process, the log messages will spread over the different syslog >>> files. >>>> >>>> If you state what concrete syslog deamon you'll use, I may have concrete >>>> configuration instructions for this. >>>> >>>> >>>> >>>> Sincerely >>>> >>>> Guido >>>> >>>> >>>>> Hello, >>>>> >>>>> I am using LXC a long time. I have problem with syslog messages. >>>>> They are corrupted. >>>>> >>>>> For example: >>>>> >>>>> >>>>> Jan 24 09:05:27 lx3 kernel: 78e1601e8c48:00 =.27T2.1N4S0R0 = 6 TDP5 = = >>>>> 6241.950 hrwl:6n:OIe13Ue0Ac4ee1601e8c4004009S=2879S1..3L=4O00R=0T=3D2 >>>>> O=PP58D=2E1 62e:R:e.Oe =48:60:89:05:9R78.D13.L1T0 C0T5D2R= =9P6E24091 >>>>> owl6eRIt6UtMc7:11:ed:00:00C2.2S703E4OxP=0L3=9OUS58T2N4eh >>>>> Ca78:60:89:05:9R78.D13.L1T0 C0T5D2R= =9P6E2<6>[224021.773178] >>>>> Shorewall:vl632net:DROP:IN=eth1.63 OUT=eth0 >>>>> MAC=ca:47:e8:e9:17:61:00:19:e7:8d:c9:42:08:00:45:00:00:90 >>>>> SRC=172.28.27.27 DST=172.30.0.31 LEN=144 TOS=0x00 PREC=0x00 TTL=253 >>>>> ID=6529 PROTO=UDPSP=59D= = ::::::::::: C7222D=20. N4T=0PCx L5I61RODS=1 >>>>> T6L=4[204519]Soelv3eDPNt. Tt Ca78971097d92805000R1... T7301E1 Sx E00T2 >>>>> =0PTU T48P1 N2 >>>>> >>>>> Exist any solution? Is possible to isolate syslogs between containers? >>>>> >>>>> Thnank You and best regards, >>>>> >>> >>> -- >>> Miroslav Lednický, >>> Fakultní nemocnice u sv. Anny v Brně > > -- > Miroslav Lednický, > Fakultní nemocnice u sv. Anny v Brně > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_jan > _______________________________________________ > Lxc-users mailing list > Lxc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-users ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
