Chris Breemer writes:
> In the midst of all that funky Samba stuff, I've a question about good
> old plain ftp. Has anybody run that via inetd yet? If so, how ? It seems
> a waste to have a separate monitor job running (FTPMON) next to inetd.

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.

>  Received call for: ftp tcp
>  SOFTWARE ABORT   (FSERR 32)
>  FILE OPEN ERROR (PASCERR 692)
>  FILE IS 'INPUT'
>  ABORT: FTPSRVR.ARPA.SYS
>  NM SYS   a.00a82288 dbg_abort_trace+$24
>  NM PUB   151.003c7a34 P__PASCFERROR+$3e0
>  NM PROG  651.0001916c _start+$b4

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.

This is one of those POSIX smoothing issues that makes life interesting.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)