[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#541872: debian-policy: identical notation for disabled-by-user and auto-generated entries in /etc/inetd.conf



On Thu, Aug 20, 2009 at 11:08:40AM +0100, Roger Leigh wrote [edited]:
> For this reason, I would prefer to stick with perl, but it's your choice.

Sure, I'll just have to add way more test cases :)

> Since xinetd already has the parsing code, it might be worth looking
> at that as a starting point (xinetd/confparse.c, I think).

Good point (xinetd/parse.c actually)

> Sounds good.  inetd-base might be a slightly better name, since it's
> something all the inetd implementations will depend upon (but packages
> /providing/ inetd fragments won't need to, since the TTBOMK file
> triggers happen transparently).  This will mean these packages won't
> need to do anything except provide the config fragment.

That's fine by me. I understand that renaming a pkg can be done transparently
(wrt rdepends) using replaces+provides+conflicts against update-inetd
(according to devref 5.9.3). In that case I'll use /etc/inetd.base.d instead
of /etc/inetd.conf.d

(I suppose it's OK to close bugs belonging to update-inetd from the changelog
of inetd-base)

> I'm not sure if any additional steps would need to be taken on removal, e.g.
> if the service should be stopped in prerm.

If I understand correctly, this is an issue only for standalone servers, not
for services instantiated by inetd (those will seize to run as soon as the
server binary is gone and any pending instances exit).

Removed packages should definitely call update-inetd, to give it a chance to
go through the fragments in /etc/inetd.base.d, set ``disable=yes'' to those
that refer to non-existent server binaries, and update the actual (x)inetd
configuration. (Otherwise (x)inetd will spam logs for failing to invoke
missing servers)

-S

-- 
debtags-organised WNPP bugs: http://members.hellug.gr/serzan/wnpp



Reply to: