[Bug 280053] Re: xinetd enabled is not overruled by disable in service declaration

2013-12-19 Thread Launchpad Bug Tracker
[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.net/bugs/280053

Title:
  xinetd enabled is not overruled by disable in service declaration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/280053/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 280053] Re: xinetd enabled is not overruled by disable in service declaration

2013-10-20 Thread LtWorf
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 _can_ prevent a service from being enabled, but not it _will_,
meaning that no deterministic behaviour is indicated for this case.

** Changed in: xinetd (Ubuntu)
   Status: Confirmed = Incomplete

-- 
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/280053

Title:
  xinetd enabled is not overruled by disable in service declaration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/280053/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 280053] Re: xinetd enabled is not overruled by disable in service declaration

2013-10-20 Thread Klaus S. Madsen
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 the entire man-page and determined that my
understanding is wrong, please feel free to close the bug. I have no
need to argue further about a 5 year old bug-report that no one has
looked at in 4 years, and which exists in a piece of unloved legacy
software.

-- 
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/280053

Title:
  xinetd enabled is not overruled by disable in service declaration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinetd/+bug/280053/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 280053] Re: xinetd enabled is not overruled by disable in service declaration

2009-10-19 Thread Chuck Short
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 are a member of Ubuntu
Server Team, which is subscribed to xinetd in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 280053] Re: xinetd enabled is not overruled by disable in service declaration

2009-10-14 Thread Klaus S. Madsen
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
documentation still states that the disable = yes line in the service
configuration takes precedence.

So this bug is still present in Karmic.

-- 
xinetd enabled is not overruled by disable in service declaration
https://bugs.launchpad.net/bugs/280053
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs