🚀 go-pugleaf

In <1992Dec18.135727.4601@sonyd1.Broadcast.Sony.COM> lilb@sony.compuserve.com (Bruce Lilly) writes:
>Does innd have to be running continuously, or can it be run on an
>as-required basis from inetd?
If you do not need to use NNTP for newsreaders, you can run it out
of inetd, sort of.  It will take a bit of finessing (e.g., adding "-n"
to the expire invocation in news.daily), but it should probably work.
It's not intended to be run that way, however, so I won't feel obligated
to answer any questions about such a set-up. :-)

>Aside from a socket emulation library, what does INN require
>(does it require BSD-hacked signal(3) calls, e.g.)?
Non-blocking sockets.  Ability to do malloc(n*1024) where "n" > 64.
Ability to select on sockets which have been dup'd across an exec.  As for
signals, INN uses the simplest and safest signal-handling possible:  set
global flag, reset handler, and return.  Other then that I haven't heard
of any real portability issues.
	/r$