[Coco] Tutorial on Telnet/inetd on Coco3 DW4 (is there one?)

[Gene Heskett]

On Thursday 11 October 2012 16:37:56 Aaron Wolfe did opine:

> > So, only Aaron can answer this question:  Does inetd ever close that
> > path to /sys/inetd.conf?  Seems like it should once it has read it,
> > but, even with it redirected to another screen, it does have an open
> > path to /DD according to proc.
> > 
> > If it does hold it open, why?  And if "kill"ed, does it clean up befor
> 
> Well, actually Boisy wrote inetd so I am not entirely sure but the code
> is in nitros9 so we can take a look.  I know that inetd does some
> fairly fancy manipulation of io handles and it may just be confusing
> something, or it may really keep inetd.conf open.
> 
> It has 2 phases, the first is to read the file and send listen requests
> to DW so the server knows to routes incoming connections to it.  The
> second phase listens for connection announcements from the server,
> forks for each, opens a new virtual xhannel, attaches to the incoming
> connection, maps its own stdin and stdout to that new channel, and
> execs the command specified in inetd.conf.  so it may be holding
> inetd.conf open for use in the second phase, dunno.
> 
At this point, neither do I.  It has one I$Open, 9 I$#Dup's, and 12 
I$Close's in it.  And not enough comments. :(

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
"Life is a garment we continuously alter, but which never seems to fit."
		-- David McCord