Ticket #261 (closed defect: invalid)
debathena-discuss-server shouldn't assume inetd
Reported by: | mitchb | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | -- | Keywords: | |
Cc: | Fixed in version: | ||
Upstream bug: |
Description
When I took the debathena-discuss-server update this
morning, I noticed the following message:
The following line will be added to your /etc/inetd.conf file:
discuss\tstream\ttcp\tnowait\tdiscuss\t/usr/sbin/discussd
If you are indeed using xinetd, you will have to convert the
above into /etc/xinetd.conf format, and add it manually. See
/usr/share/doc/xinetd/README.Debian for more information.
First, the "\t"s above are literal - they displayed as "\t"
on the screen, which is probably an error.
Second, even Hardy, which is the oldest supported Ubuntu
release, uses xinetd, so the package should probably
know how to detect and configure xinetd correctly.
Change History
comment:1 in reply to: ↑ description Changed 15 years ago by kcr
comment:2 in reply to: ↑ description Changed 15 years ago by andersk
- Status changed from new to closed
- Resolution set to invalid
Replying to mitchb:
Second, even Hardy, which is the oldest supported Ubuntu
release, uses xinetd, so the package should probably
know how to detect and configure xinetd correctly.
Ubuntu doesn’t use xinetd by default.
$ aptitude search '~D^openbsd-inetd$' | wc -l 64 $ aptitude search '~D^xinetd$' p xmlsysd - wulfware daemon to extract data from clust
Though as kcr says, it should work fine anyway.
At least in debian, xinetd is usually run with the -inetd_compat option, so it reads /etc/inetd.conf, and that message is a bug in update-inetd.