INN commit: trunk (doc/FAQ scripts/innreport_inn.pm)

[INN Commit]

    Date: Saturday, October 3, 2009 @ 10:54:49
  Author: iulius
Revision: 8646

inndstart is no longer used (it was removed in INN 2.5.0)
so we mention it in our FAQ.

Modified:
  trunk/doc/FAQ
  trunk/scripts/innreport_inn.pm

--------------------------+
 doc/FAQ                  |   16 +++++++++-------
 scripts/innreport_inn.pm |    9 ---------
 2 files changed, 9 insertions(+), 16 deletions(-)

Modified: doc/FAQ
===================================================================
--- doc/FAQ	2009-10-03 17:53:57 UTC (rev 8645)
+++ doc/FAQ	2009-10-03 17:54:49 UTC (rev 8646)
@@ -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

Modified: scripts/innreport_inn.pm
===================================================================
--- scripts/innreport_inn.pm	2009-10-03 17:53:57 UTC (rev 8645)
+++ scripts/innreport_inn.pm	2009-10-03 17:54:49 UTC (rev 8646)
@@ -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