Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 590734 - sys-apps/xinetd: -inetd_compat: /etc/inetd.conf port numbers not handled properly
Summary: sys-apps/xinetd: -inetd_compat: /etc/inetd.conf port numbers not handled prop...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-08 08:00 UTC by Pavel Šimerda (pavlix)
Modified: 2016-08-10 11:42 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Šimerda (pavlix) 2016-08-08 08:00:43 UTC
I attempted to install classing inetd using one service per line inetd.conf format and it instead installed xinetd with the following issues.

1) It doesn't read inetd.conf by default.

2) Even when configured, it doesn't support inetd.conf syntax properly. Even the simplest example won't work, see below.

/etc/inetd.conf:

443 stream tcp nowait root /bin/nc nc localhost 22

xinetd -d -inetd_compat:

16/8/8@09:47:15: ERROR: 8487 {service_fill} Port not specified and can't find service: 443 with getservbyname
Comment 1 Pavel Šimerda (pavlix) 2016-08-08 08:01:39 UTC
Also sys-apps/netkit-base apparently only contains inetd and should therefore be renamed to netkit-inetd.
Comment 2 SpanKY gentoo-dev 2016-08-10 02:05:24 UTC
pretty sure you can make that same argument about many of the virtual replacements.  it's not terribly important as we haven't defined the virtual as "must handle /etc/inetd.conf exactly".

don't file multiple issues in a single bug.  every independent issue gets its own bug.  this bug is only about xinetd parsing of inetd.conf now.
Comment 3 Pavel Šimerda (pavlix) 2016-08-10 08:57:38 UTC
(In reply to SpanKY from comment #2)
> don't file multiple issues in a single bug.  every independent issue gets
> its own bug.  this bug is only about xinetd parsing of inetd.conf now.

I didn't know how to file properly in this case. If xinetd parsing is fixed to support at least basic inetd.conf syntax then I would consider adding the parameter by default so that xinetd passes as a drop-in replacement for inetd.

Note: I do like inetd syntex due to its simplicity. I always need to search for the way to tell xinetd to work directly with port numbers and even then the xinetd.conf records are rather verbose.
Comment 4 SpanKY gentoo-dev 2016-08-10 09:55:08 UTC
(In reply to Pavel Šimerda (pavlix) from comment #3)

i don't see value in adding inetd.conf support by default.  it's rarely used nowadays as packages install xinetd config files instead.  for the rare people (such as yourself) who want simpler/less secure options, you can easily tweak the init.d config settings.
Comment 5 Pavel Šimerda (pavlix) 2016-08-10 11:42:31 UTC
(In reply to SpanKY from comment #4)
> (In reply to Pavel Šimerda (pavlix) from comment #3)
> 
> i don't see value in adding inetd.conf support by default.  it's rarely used
> nowadays as packages install xinetd config files instead.  for the rare
> people (such as yourself) who want simpler/less secure options, you can
> easily tweak the init.d config settings.

OK.