[jaunty] xinetd upgrade invokes itox incorrectly

[philip]

A mass-upgrade of Jaunty Beta got me xinetd 1:2.3.14-7ubuntu1. A message from the installer,
copied below, shows it trying to convert an old-style "inetd" setup line to the new-style "xinetd"
format. It fails, because the converter program "itox" is not given enough options. Watch this:

--------- IMPORTANT INFORMATION FOR XINETD USERS ----------
The following line will be added to your /etc/inetd.conf file:

9572 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdswapd

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.
Suggested entry (automatically converted using itox):

service 9572
{
        socket_type = stream
        protocol = tcp
        wait = no
        user = nobody
You must use option -daemon_dir if you use tcpd
-----------------------------------------------------------
The last line here is emitted by /usr/sbin/itox. That utility seems to be getting
invoked something like this:
 echo "9572 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdswapd" | itox
What it wants is something more like the following
 echo "9572 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdswapd" | itox -daemon_dir /dev/null

The final particle here looks should probably be some kind of directory name.
At this point my detective skills run out: I don't know what directory to specify.
/dev/null is guaranteed to be wrong, but even with that wrong choice the itox utility
at least survives long enough to produce a syntatically correct entry for use
with xinetd.

~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

[Chuck Short (zulcss)]

Hi,
I was wondering if you were still having this problem.

Regards
chuck

[philip (philip-tidepool)]

Chuck Short wrote:

> I was wondering if you were still having this problem.

Thanks for following up on this, Chuck.

After noting the issue on the bug-tracker, I hacked together
some workaround and moved on. Unfortunately this means that
I can't answer your question properly: all I can say is that
the problem is no longer a concern for me ... which falls
short of saying a bug has definitely been squashed.

Sorry I can't be more encouraging on the technical side;
on the human side, I repeat my gratitude for your assiduity.

Philip

[Chuck Short (zulcss)]

User is no longer to replicate. Thanks for the bug report.

Regards
chuck