🚀 go-pugleaf

In article <1gll86INNhsv@meaddata.meaddata.com> dem@meaddata.com (David Myers) wrote:
>
>   Also, our news machine has lots of memory.  This is fairly
>important for INN.   

I'd appreciate it if somebody could be more specific about the
INN memory requirements:
a)	exactly how much is ``lots''?
b)	are we talking about physical RAM or virtual memory?
c)	does ``fairly important'' mean that INN will crash and
	burn if it can't malloc  more than 2.5 MB of VM (e.g.)?

>   I've had very few problems with INN.  One problem that cropped up
>at one point (but that has since vanished - odd) is an occasional
>crash of the innd daemon.  This is rather serious, as it prevents
>users from reading news via NNTP.  The easy solution is to write a
>wrapper script that restarts innd should it fail.  I haven't seen a
>failure in almost two months now, though.

Does innd have to be running continuously, or can it be run on an
as-required basis from inetd (suitable for machines with low
volume feeds and only occasional newsreader connections (nntpd
can be run from inetd))?

What other underlying assumptions and requirements exist for
INN? For example, somebody else claimed that because INN can
write to a pipe rather than to a disk file, it's performance can
be better than C news'.  That assumes that a pipe is
fundamentally different from a disk file, which is certainly not
the case for many varieties of the UNIX(R) operating system.
Aside from a socket emulation library, what does INN require
(does it require BSD-hacked signal(3) calls, e.g.)?

-- 
    Bruce Lilly, Product Manager,      | bruce@Broadcast.Sony.COM
    Routers, Peripherals & Still Store,| uunet!sonyusa!sonyd1!bruce
    Sony, 3 Paragon Drive, Montvale,   | lilb@sony.compuserve.com (slow)
    NJ 07645-1735  |  Telephone: +1 201 358 4161  |  FAX: +1 201 358 4274