[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 6/9: Day-to-day operation and changes to the system
Previous Document: (6.5) How do I talk to innd from C or Perl?
Next Document: (6.7) How do I moderate a mailing list?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 6/9: Day-to-day operation and changes to the system
Previous Document: (6.5) How do I talk to innd from C or Perl?
Next Document: (6.7) How do I moderate a mailing list?
(6.6) After a crash.
"What do I do after a system crash?" INN handles crashes pretty well. If there are any problems they get cleaned up by the nightly expire. About once a month you might want to run "makehistory -buv" to look for "lost" articles. Check the man page for "makehistory" for more information. (The man page for "makehistory" is in the news-recovery man page until INN 1.4). The manpage is a little unclear about the '-n' flag. If used alone (e.g. makehistory -n) it does not rebuild the dbz files. But if used in conjunction with -bu (e.g. makehistory -bunv) it does not pause the server. See also #5.11.
Top Document: INN FAQ Part 6/9: Day-to-day operation and changes to the system
Previous Document: (6.5) How do I talk to innd from C or Perl?
Next Document: (6.7) How do I moderate a mailing list?
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