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: socket activation for INN (Russ Allbery)
2. Re: socket activation for INN (Julien ?LIE)
3. Re: socket activation for INN (Russ Allbery)
----------------------------------------------------------------------
Message: 1
Date: Mon, 19 May 2014 11:31:10 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: socket activation for INN
Message-ID: <[email protected]>
Content-Type: text/plain
[email protected] (Marco d'Itri) writes:
> Would you accept a patch similar to this one?
> I have been using it for a while with inn 1.x and it works well.
> http://anonscm.debian.org/gitweb/?p=users/md/inn.git;a=commitdiff;h=a1ca667dd50b6578130f12a80512e3e8267b355a
This generally looks good to me. I particularly like the status
notification.
There are a few nits:
* Never use sprintf in new INN code. INN provides snprintf, which can be
used if there's no good way to structure the code to use asprintf.
asprintf is strongly preferred if it's possible to structure the code to
use it.
* rra-c-util provides portability for libsystemd-daemon, which should be
used instead of calling pkg-config directly and which will also handle
silent degredation if systemd isn't available. The logic in this patch
for innd will have to change a little to continue on with normal startup
if systemd is not available.
* INN should be able to listen to multiple sockets. We already configure
it that way now. I'm not sure what additional glue will be required.
rra-c-util may need some additional portability glue for sd_is_socket,
since I don't think I've needed that before.
Ideally, we should also use socket activation for the ctlinnd socket, but
that can wait until later.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
Message: 2
Date: Mon, 19 May 2014 21:11:56 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: socket activation for INN
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Russ,
> Ideally, we should also use socket activation for the ctlinnd socket, but
> that can wait until later.
Wouldn't it also be useful for nnrpd running as a daemon? (especially
for the one listening on the TLS NNTP port)
--
Julien ?LIE
? Et maintenant, passons ? table. Toi aussi, mon fils ! ? (C?sar)
------------------------------
Message: 3
Date: Mon, 19 May 2014 13:12:41 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: socket activation for INN
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Julien ?LIE <[email protected]> writes:
> Hi Russ,
>> Ideally, we should also use socket activation for the ctlinnd socket, but
>> that can wait until later.
> Wouldn't it also be useful for nnrpd running as a daemon? (especially for
> the one listening on the TLS NNTP port)
Yes, although it's less pressing than for innd because an inetd daemon
works fine there (and therefore so does systemd in inetd emulation mode,
if you don't want to run a separate inetd daemon).
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 62, Issue 3
******************************************
