[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 1/9: General Information
Previous Document: (1.12) Can I run INN on my UUCP-only machine?
Next Document: (1.14) Does INN implement NOV, xthread (trn) or xuser/xmotd (tin) commands?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 1/9: General Information
Previous Document: (1.12) Can I run INN on my UUCP-only machine?
Next Document: (1.14) Does INN implement NOV, xthread (trn) or xuser/xmotd (tin) commands?
(1.13) Suppose I have a 286 machine?
Won't work. INN is designed to be a memory hog; a server that has been up for a few days while will have a working set size of a few to several megabytes, although not all of it will be resident. For example, the server keeps the active file and list of who gets what in memory, as well as all articles that it is receiving. Unless you can do things like "malloc(64 * 1024)" without pain, INN won't work on your machine.
Top Document: INN FAQ Part 1/9: General Information
Previous Document: (1.12) Can I run INN on my UUCP-only machine?
Next Document: (1.14) Does INN implement NOV, xthread (trn) or xuser/xmotd (tin) commands?
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
hwr@pilhuhn.de (Heiko W.Rupp)
Last Update December 05 2008 @ 00:13 AM