Re: [Lxc-users] LXC on Debian Squeeze
On Mon, Sep 27, 2010 at 10:13 PM, Daniel Lezcano daniel.lezc...@free.fr wrote:
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.
So, tracing the two open fds as you suggested
lxc-start: inherited fd 7 on pipe:[5329]
lxc-start: inherited fd 9 on pipe:[5333]
in the following tree
init─┬─acpid
├─console-kit-dae───63*[{console-kit-da}]
├─cron
├─2*[dbus-daemon]
├─dbus-launch
├─dhclient
├─gdm───gdm─┬─Xorg
│ └─fluxbox─┬─ssh-agent
│ ├─urxvt───bash───su───bash
│ └─xterm───bash───su───bash───pstree
revealed they are both open starting with the second gdm process
down to the leaf bash processes.
The first gdm process had only fd 7 on pipe:[5329] open and finally
init had none of these pipes.
As you can see, I have exchanged xmonad for fluxbox and in
addition to urxvt I tried xterm without any change.
To send the bugreport to a proper place, which process should be
responsible for closing those fds? gdm?
Thanks,
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
Re: [Lxc-users] LXC on Debian Squeeze
On 09/28/2010 09:21 AM, Frank Bauer wrote:
On Mon, Sep 27, 2010 at 10:13 PM, Daniel Lezcanodaniel.lezc...@free.fr
wrote:
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.
So, tracing the two open fds as you suggested
lxc-start: inherited fd 7 on pipe:[5329]
lxc-start: inherited fd 9 on pipe:[5333]
in the following tree
init─┬─acpid
├─console-kit-dae───63*[{console-kit-da}]
├─cron
├─2*[dbus-daemon]
├─dbus-launch
├─dhclient
├─gdm───gdm─┬─Xorg
│ └─fluxbox─┬─ssh-agent
│ ├─urxvt───bash───su───bash
│ └─xterm───bash───su───bash───pstree
revealed they are both open starting with the second gdm process
down to the leaf bash processes.
The first gdm process had only fd 7 on pipe:[5329] open and finally
init had none of these pipes.
As you can see, I have exchanged xmonad for fluxbox and in
addition to urxvt I tried xterm without any change.
To send the bugreport to a proper place, which process should be
responsible for closing those fds? gdm?
Yes, I think so.
I found that :
http://www.mail-archive.com/debian-bugs-clo...@lists.debian.org/msg270073.html
It was not considered as a bug but IMO it was not looked closely enough,
having a fd inherited in all the child processes is a bug :)
Maybe you can reopen it.
Thanks
-- Daniel
--
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
Re: [Lxc-users] LXC on Debian Squeeze
Daniel Lezcano daniel.lezc...@free.fr writes:
On 09/28/2010 09:21 AM, Frank Bauer wrote:
On Mon, Sep 27, 2010 at 10:13 PM, Daniel Lezcanodaniel.lezc...@free.fr
wrote:
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.
So, tracing the two open fds as you suggested
lxc-start: inherited fd 7 on pipe:[5329]
lxc-start: inherited fd 9 on pipe:[5333]
in the following tree
init─┬─acpid
├─console-kit-dae───63*[{console-kit-da}]
├─cron
├─2*[dbus-daemon]
├─dbus-launch
├─dhclient
├─gdm───gdm─┬─Xorg
│ └─fluxbox─┬─ssh-agent
│ ├─urxvt───bash───su───bash
│ └─xterm───bash───su───bash───pstree
revealed they are both open starting with the second gdm process
down to the leaf bash processes.
The first gdm process had only fd 7 on pipe:[5329] open and finally
init had none of these pipes.
As you can see, I have exchanged xmonad for fluxbox and in
addition to urxvt I tried xterm without any change.
To send the bugreport to a proper place, which process should be
responsible for closing those fds? gdm?
Yes, I think so.
I found that :
http://www.mail-archive.com/debian-bugs-clo...@lists.debian.org/msg270073.html
It was not considered as a bug but IMO it was not looked closely enough,
having a fd inherited in all the child processes is a bug :)
Maybe you can reopen it.
I couldn't agree more, please reopen the bug. I don't get why this
doesn't look like an actual leak.
--
Thanks,
Feri.
--
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
Re: [Lxc-users] LXC on Debian Squeeze
Frank Bauer frank.c.ba...@gmail.com writes: squeeze:~# lxc-start -n container lxc-start: inherited fd 7 on pipe:[4220] lxc-start: inherited fd 9 on pipe:[4224] You can get your shell to close those file descriptors by # lxc-start -n 7- 8- But best would be to find out who leaked those, and fix the real breakage. Btw. lxc works for me on squeeze, but I use application containers only. -- Regards, Feri. -- 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
Re: [Lxc-users] LXC on Debian Squeeze
On 09/27/2010 09:56 PM, Frank Bauer wrote: On Mon, Sep 27, 2010 at 1:15 PM, Ferenc Wagnerwf...@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
