[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.54) Expire is slooooooow
Next Document: (7.56) I upgraded to INN 1.5.1, and peers have trouble feeding me.
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.54) Expire is slooooooow
Next Document: (7.56) I upgraded to INN 1.5.1, and peers have trouble feeding me.
(7.55) Why are multiple innwatch's running?
From: Jim Dutton <jimd@dutton4.it.siu.edu> Currently, "nobody" seems to verify whether an innwatch task is already executing before innwatch is started up in rc.news. Also, when innd is terminated via ctlinnd shutdown, innwatch is not affected (eg; it is left running). Since rc.news always starts an innwatch task, if innd is shutdown for maintenance, it is necessary to remember to ALSO kill the innwatch task and its attendant "sleeper" task, thus ensuring that there is no innwatch running when rc.news is executed to restart innd (assuming that this is how innd is restarted, of course).
Top Document: INN FAQ Part 7/9: Problems with INN already running
Previous Document: (7.54) Expire is slooooooow
Next Document: (7.56) I upgraded to INN 1.5.1, and peers have trouble feeding me.
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 October 13 2008 @ 00:13 AM