[Expired for xinetd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xinetd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.
I reported it because I believe that disable should take precedence from
my reading of the man-page. Furthermore making disable overrule enable
is the most secure thing to do if there is any ambiguity about whether a
service should be enabled or disabled in the configuration file.
If you have read
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
Thanks for the bug report. Setting this to confirmed.
Regards
chuck
** Changed in: xinetd (Ubuntu)
Status: Incomplete => Confirmed
--
xinetd enabled is not overruled by disable in service declaration
https://bugs.launchpad.net/bugs/280053
You received this bug notification because you ar
I've tested it, by downloading the Karmic Koala Kubuntu beta live image,
running apt-get update, and then apt-get install xinetd to install the
xinetd daemon.
Altering the /etc/xinetd.conf file as described in the original bug
report, still enables the chargen service. I also verified that the
doc
