-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/06/2011 12:49 PM, Stéphane Graber wrote:
On 10/06/2011 12:51 AM, Daniel Baumann wrote:
On 10/06/2011 03:48 AM, Stéphane Graber wrote:
though a good part of that will probably have to happen in
Debian
which is why the bug should be
On Wed 2011-10-05 (21:48), Stéphane Graber wrote:
The problem is: when I stop xinetd on the host with command
/etc/init.d/xinetd stop
this stops all LXC container xinetd processes, too!
Can you file a bug here: http://launchpad.net/ubuntu/+source/xinetd/+filebug
I have already done it
On Thu 2011-10-06 (09:14), Ulli Horlacher wrote:
Then attach the patch to the bug making sure that it's flagged as a
patch. This should ensure someone will look at it, sadly not for Oneiric
(11.10) but hopefully for Precise (12.04).
Launchpad lets you mark a bug as affecting multiple
Quoting Ulli Horlacher (frams...@rus.uni-stuttgart.de):
On Thu 2011-10-06 (09:14), Ulli Horlacher wrote:
Then attach the patch to the bug making sure that it's flagged as a
patch. This should ensure someone will look at it, sadly not for Oneiric
(11.10) but hopefully for Precise
I have an Ubuntu LXC hosts with several containers running internet
services via xinetd.
Sometimes the container services died without any reason and no logfile
entry. First, I thought LXC is not that stable as I hoped, but now I
found the bug inside /etc/init.d/xinetd !
The problem is: when I
On 10/05/2011 06:43 PM, Ulli Horlacher wrote:
I have an Ubuntu LXC hosts with several containers running internet
services via xinetd.
Sometimes the container services died without any reason and no logfile
entry. First, I thought LXC is not that stable as I hoped, but now I
found the bug
On 10/05/2011 12:43 PM, Ulli Horlacher wrote:
I have an Ubuntu LXC hosts with several containers running internet
services via xinetd.
Sometimes the container services died without any reason and no logfile
entry. First, I thought LXC is not that stable as I hoped, but now I
found the bug
On 10/06/2011 03:48 AM, Stéphane Graber wrote:
though a good part of that will probably have to happen in Debian
which is why the bug should be filled in debian in the first place:
http://www.debian.org/Bugs/Reporting
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:
