Patch was accepted upstream and it will be in their next release.
** Changed in: xinetd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bug
Where in the documentation does it say that the disable = yes takes
precedence?
In the quoted text:
Note that the service "disable" attribute and
"DISABLE" flag can prevent a service from being
enabled despite being listed in this attribute.
It _ca
** Changed in: xinetd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bugs/868538
Title:
/etc/init.d/xinetd kills LXC container's xin
** Changed in: xinetd (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bugs/868538
Title:
/etc/init.d/xinetd kills LXC container's xinetd
Patch forwarded to upstream.
https://github.com/xinetd-org/xinetd/pull/4
** Changed in: xinetd (Ubuntu)
Status: New => Fix Committed
** Changed in: xinetd (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server T
This was done because that's the default inetd behavior and xinetd must
be usable as drop-in replacement.
You could still use xinetd disabling the compatibility.
** Changed in: xinetd (Ubuntu)
Assignee: (unassigned) => LtWorf (tiposchi)
** Changed in: xinetd (Ubuntu)
** Changed in: xinetd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bugs/561475
Title:
when sysctl net.ipv6.bindv6only=1, xinetd can not bind
In general the open group defines that parameter to be 0 by default:
http://pubs.opengroup.org/onlinepubs/007904875/functions/xsh_chap02_10.html
So all the developers assume it to be 0 unless they set it explicitly in
their code.
You might want to patch your broken application instead of reportin
