Hi William,
> I came across the following in the innd(8) man page:
>> To use IPv6, innd must be started by inndstart.
>> Mmm. I thought inndstart was retired some time ago, and I know just using rc.news is enough. Maybe the docs are laggin?
Are you sure that you properly updated INN?
This sentence is not present in INN 2.5.0; it was removed
from innd(8) in 2003 when Russ removed inndstart and startinnfeed.
I only see two files that still need to be updated (note that the FAQ
wasn't in Subversion yet in 2003). Patch below.
Julien
Index: scripts/innreport_inn.pm
===================================================================
--- scripts/innreport_inn.pm (révision 8592)
+++ scripts/innreport_inn.pm (copie de travail)
@@ -1775,15 +1775,6 @@
return 1 if $left =~ /^starttls: \S+ with cipher \S+ \(\d+\/\d+ bits\) no authentication$/o;
}
########
- ## inndstart
- if ($prog eq "inndstart") {
- # cant bind Address already in use
- # cant bind Permission denied
- return 1 if $left =~ /cant bind /o;
- # cant setgroups Operation not permitted
- return 1 if $left =~ /cant setgroups /o;
- }
- ########
## overchan
if ($prog eq "overchan") {
# times
Index: doc/FAQ
===================================================================
--- doc/FAQ (révision 8642)
+++ doc/FAQ (copie de travail)
@@ -502,9 +502,11 @@
Subject: 3.1. INN won't start after a new installation
-The most common cause of this problem is that inndstart isn't setuid root.
-inndstart must be installed owned by root and group news, mode 4550. The
-ls -l output for inndstart should look something like:
+The most common cause of this problem is that inndstart isn't setuid root
+(please note that it only affects versions prior to INN 2.5.0 because
+inndstart was removed in INN 2.5.0). inndstart must be installed owned
+by root and group news, mode 4550. The ls -l output for inndstart should
+look something like:
-r-sr-x--- 1 root news 53768 Jan 8 00:47 inndstart*
@@ -572,10 +574,10 @@
Subject: 3.6. Can't get debugging information out of INN
The INN startup process is quite complicated, involving the rc.news shell
-script and the setuid inndstart wrapper. This can make it rather
-difficult to get enough debugging information out of it to determine
-what's going wrong if it's crashing immediately after startup or otherwise
-having serious difficulties.
+script (and the setuid inndstart wrapper for versions of INN prior to 2.5.0).
+This can make it rather difficult to get enough debugging information out
+of it to determine what's going wrong if it's crashing immediately after
+startup or otherwise having serious difficulties.
One approach is to run innd by hand directly, giving it the -d option.
This requires setting up a configuration where innd doesn't need to bind