inetd grief

[Jay Benfield <jay@xxxxxxxxxxxxx>]

Lots of questions recently :-)

I had my workstation (RedHat 5.2) bolted down super tight - pretty much
EVERY service in inetd.conf commented out and stringent tcp_wrappers
were in effect. 

Well, I now have a need to allow pop-3 and ftp. So, I uncomment those
lines
in inetd.conf - restart inetd - and I get a SERVICE UNAVAILABLE - when
trying to attempt such connections. 
 
I say ok - maybe my hosts.allow/deny are too strict. So, just for the
heck
of it, I rename the originals - and make another pair - implicitely
allowing e v e r y t h i n g. 

So - everything access wise should be set. But still no dice. So, I tail
the messages and secure logs in /var/log. I'm getting messages like
these:

Mar  4 10:19:17 netsrv3 ipop3d[825]: connect from 206.150.112.54
Mar  4 10:19:17 netsrv3 ipop3d[825]: error: cannot execute
/usr/sbin/ipop3d: No such file or directory

for both in.ftpd and in.pop3d. Now this is really odd. When a connect
comes in, inetd is SUPPOSED to run the command line in inetd.conf
associated with service. For instance, ftp would execute:

/usr/sbin/tcpd in.ftpd -l -a

and pop3 would execute:

/usr/sbin/tcpd in.pop3d

So how and why is it calling /usr/sbin/in.ftpd and /usr/sbin/in.pop3d?
Makes no sense. So I figure I've done considerable hacking around in the
inetd.conf, maybe there's some line feeds or something in there. So I
FTP
over another copy of inetd.conf from our main server - and HUP inetd. 

Still no dice. I then re-installed the FTP package and tcp_wrappers. 

Any ideas? 

- Jay