On 09/27/2010 09:56 PM, Frank Bauer wrote: > On Mon, Sep 27, 2010 at 1:15 PM, Ferenc Wagner<wf...@niif.hu> wrote: > >> You can get your shell to close those file descriptors by >> >> # lxc-start -n 7<&- 8<&- >> > I'll try that when I get to my laptop. > > >> But best would be to find out who leaked those, and fix the real >> breakage. >> > I'm running fairly plain system: > linux -> upstart -> X -> gdm -> Xmonad -> urxvt -> bash -> lxc > so I will try to exchange a component by component to find the cause > (although this is the same combination that used to work in the past).
Maybe it would be easier to check first if you have this fd in bash with ls -al /proc/<pid>/fd and then follow up the hierarchy to find the first process who introduced this fd. Inherited file descriptors were not checked before, it is probably the reason why it worked in the past. >> Btw. lxc works for me on squeeze, but I use application containers only. >> > Thanks for the report. > > Frank > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Lxc-users mailing list > Lxc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-users > > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
