Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. Update of supported systems (Julien ?LIE)
   2. Re: INN 2.6.4 release candidate (Marco d'Itri)


----------------------------------------------------------------------

Message: 1
Date: Sat, 9 Jan 2021 23:45:23 +0100
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Update of supported systems
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi all,

I suggest an update to the list of supported systems at the beginning of 
INSTALL:
   https://www.eyrie.org/~eagle/software/inn/docs/install.html

I am unsure current versions of INN still work fine with very old 
versions listed...

We currently say:

"""
As much as possible, INN is written in portable C and should work on any 
Unix platform. It does, however, make extensive use of mmap(2) and 
certain other constructs that may be poorly or incompletely implemented, 
particularly on very old operating systems.

INN has been confirmed to work on the following operating systems:

     AIX 4.3
     FreeBSD 2.2.x and up
     HP-UX 10.20 and up
     Linux 2.x (tested with libc 5.4, glibc 2.0 and up)
     Mac OS X 10.2 and up
     NetBSD 1.6 and up
     OpenBSD 2.8 and up
     SCO 5.0.4 (tested with gcc 2.8.1, cc)
     Solaris 2.5.x and up
     UnixWare 7.1
     UX/4800 R11 and up
"""


Are there people here running INN 2.6.x on:
- AIX 4.3 or higher?
- HP-UX 10.20 or higher?
- SCO 5 and UnixWare 7 or higher? (or now Xinuos OpenServer?)
- UX/4800 R11 or higher?

=> Please tell us, so as to update the list accordingly.  And also if 
you are running INN on a system not listed here:  Minix, Windows ...?


Suggestion of new wording:

"""
INN has been confirmed to work on recent versions of the following 
operating systems:

     AIX (including 7.2)
     FreeBSD (including 12.1)
     Linux (including 4.19 and 5.10 kernels, glibc 2.28)
     macOS (including 11)
     NetBSD (including 9.0)
     OpenBSD (including 6.8)
     Oracle Solaris (including 10 and 11)

INN may also work on other operating systems like HP-UX, OpenServer or 
UnixWare but has not been confirmed to.
"""

Or say "confirmed to build" instead of work?  (I don't know either if 
there are running INN instances in AIX 7.2, Oracle Solaris 11 or OpenBSD 
6.8...).
Or without any version at all?

-- 
Julien ?LIE

??J'aime les calculs faux car ils donnent des r?sultats plus justes.??
   (Jean Arp)


------------------------------

Message: 2
Date: Sun, 10 Jan 2021 01:28:31 +0100
From: Marco d'Itri <[email protected]>
Cc: [email protected]
Subject: Re: INN 2.6.4 release candidate
Message-ID: <X/[email protected]>
Content-Type: text/plain; charset="us-ascii"

Sorry, I forgot that this patch or something to the same effect is 
needed to make systemd notifications (and future socket activation) 
work.
The reason is that systemd will only accept notifications from the
child process it spawned, so we need innd to be exec'ed by rc.news.

Without this patch inn will be stopped after one minute with messages 
like:

Jan 10 01:10:26 erode systemd[1]: inn2.service: Got notification message from 
PID 23629, but reception only permitted for main PID which is currently not 
known
Jan 10 01:11:23 erode systemd[1]: inn2.service: Failed with result 'protocol'.
Jan 10 01:11:23 erode systemd[1]: Failed to start InterNetNews.

-- 
ciao,
Marco
-------------- next part --------------
--- a/scripts/rc.news.in
+++ b/scripts/rc.news.in
@@ -157,8 +157,12 @@ if [ "$OVMETHOD" = "ovdb" ]; then
 fi
 
 ##  Start the show.
+##  When using systemd, the daemon must be started last with exec to keep
+##  the same PID of this script.
+if [ -z "$NOTIFY_SOCKET" -a -z "$LISTEN_PID" ]; then
 echo 'Starting innd.'
 eval ${WHAT} ${RFLAG} ${INNFLAGS}
+fi
 
 # Gee, looks like lisp, doesn't it?
 ${DOINNWATCH} && {
@@ -188,3 +192,9 @@ done &
 if [ -f ${PATHBIN}/rc.news.local ] ; then
     ${PATHBIN}/rc.news.local start
 fi
+
+if [ "$NOTIFY_SOCKET" -o "$LISTEN_PID" ]; then
+    echo 'Starting innd.'
+    eval exec ${WHAT} -f ${RFLAG} ${INNFLAGS}
+fi
+

------------------------------

Subject: Digest Footer

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers


------------------------------

End of inn-workers Digest, Vol 127, Issue 8
*******************************************

Reply via email to