Mark Bixby replied to my question :

>
> Yes, it does seem to be a waste, but ftpsrvr is architecturally incompatible
> with inetd.
>
> Inetd processes are supposed to terminate after they've handled the incoming
> network connection.  Ftpsrvr runs forever, waiting for new ftp connections.

It would seem that way.
But, earlier on, I had a look with GLANCE. AFAICS the one sitting there forever
is FTPMON. When a ftp connection is made, I _briefly_ see a sub-process FTPSRVR
appear. But it soon dies, and then only FTPMON is left and actually doing the
work, because the connection works fine. Doesn't make sense, or does it ?
Now which program is doing what ?

>
> Ftpsrvr is trying to open $stdin, but under inetd the network connection is
> passed as the $stdin/stdin file descriptor, and presently an MPE program
> cannot re-open a system defined file like $stdin that is really connected to
> a socket or a pipe.

Yep, I remember this now from a previous thread. Hopefully HP is going to
'smooth' this soon ...

Thanks !

        Chris Breemer
        Compuware Europe