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. Re: INN and docker default hostnames (Julien ?LIE)
2. Supporting https in actsync (ftp.isc.org) (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Sun, 29 Sep 2024 16:44:51 +0200
From: Julien ?LIE <[email protected]>
To: <[email protected]>
Subject: Re: INN and docker default hostnames
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Hi Richard,
>> How can INN determine that its installation is not finished?
>
> It can't, and it shouldn't pretend that it can.
Agreed.
> If the goal is uniqueness (the comments don't say)
[...]
> I expect innd's refusal to start would cause the Debian package setup to
> fail.
Thanks for your valuable comments.
I've just committed the proposed changes in
<https://github.com/InterNetNews/inn/issues/311> to CURRENT.
I will commit them to STABLE next week.
From NEWS:
The check for a fully qualified domain name for the local host at
startup still produces a warning in the logs but is no longer fatal.
The installation of INN was otherwise failing under some
circumstances like when creating a Docker image. Additionally, the
INN_HOSTNAME environment variable, if set and fully qualified, is
now taken by INN as the hostname.
Also added in README and INSTALL:
If you want to create a Docker image, you can find examples of
standard local Docker containers or GitHub Actions services in
projects like <https://github.com/cclauss/apt-get-inn2-docker> or
<https://github.com/greenbender/inn-docker>.
It will certainly be useful for future news admins wishing to do that.
--
Julien ?LIE
??En voyant le lit vide, il le devint.?? (Ponson du Terrail)
------------------------------
Message: 2
Date: Sun, 29 Sep 2024 16:44:49 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Supporting https in actsync (ftp.isc.org)
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Hi all,
ftp.isc.org will probably shut down the FTP protocol in a few weeks.
HTTPS will remain. See the announcement here:
http://al.howardknight.net/?STYPE=msgid&MSGI=%3C1f19a554-8a81-ce8c-8ac6-7ab1e053a632%40isc.org%3E
I'll update actsync / actsyncd to allow to fetch the active file from
external HTTP(S) sources. It currently does not handle these protocols.
The current actsync.cfg configuration file works like this:
host=ftp.isc.org
ftppath=/pub/usenet/CONFIG/active.gz
flags=-v 0 -p 80
ignore_file=actsync.ign
If ftppath is set, actsyncd downloads ftp://host/ftppath and then runs
gunzip (if the file ends with .gz) or uncompress (if the file ends with .Z).
To keep backwards-compatibility, I suggest to add two keywords (path and
protocol) and undocument ftppath (which will remain recognized as though
it were path). The default value of protocol will be "ftp".
This way,
host=ftp.isc.org
protocol=https
path=/pub/usenet/CONFIG/active.gz
flags=-v 0 -p 80
ignore_file=actsync.ign
will download protocol://host/path and the previous configuration file
will still download ftp://host/ftppath.
I don't know whether someone here uses actsync. If that's the case and
he has comments about the proposal or has proposals for any feature
requests to add to actsync, this is the time to tell :)
--
Julien ?LIE
??Je ne voudrais tout de m?me pas que Cl?op?tre m'ait dans le nez?!??
(C?sar)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 162, Issue 4
*******************************************
