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: INN2 on a Raspberry Pi 4? | Migrating between instances
      of INN2 (Julien ?LIE)
   2. Re: INN2 on a Raspberry Pi 4? | Migrating between instances
      of INN2 (Julien ?LIE)
   3. Re: INN2 on a Raspberry Pi 4? | Migrating between instances
      of INN2 (Julien ?LIE)
   4. Re: INN2 on a Raspberry Pi 4? | Migrating between instances
      of INN2 (Jesse Rehmer)


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

Message: 1
Date: Thu, 8 Feb 2024 13:35:37 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: INN2 on a Raspberry Pi 4? | Migrating between instances
        of INN2
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi Christoph,

> the biggest hog is the log compression which I changed to xz (patch not
> upstreamed for that reason)

If you think adding native support for xz compression would be useful, 
the program could be searched for in m4/compress.m4 and, if you build 
INN with the --with-log-compress=xz flag, it would normally do the trick 
(not personally tested though).
Wouldn't it correspond to your local change? (if that's the case, such a 
change could easily be merged upstream, and usable for your needs as 
well as other people's needs)

BTW, I see that this --with-log-compress configure flag is not 
documented (it is only mentioned in the output of "./configure --help").
I'll mention it in the relevant manual pages (at least INSTALL, newslog, 
news.daily and scanlogs).  Current supported methods are gzip, bzip2, 
compress and cat (meaning no compression at all).


Also, if we want to be smarter, allowing to change the compression 
method at run-time could be useful, for instance by adding a 
compressformat keyword to news.daily, which would pass it to scanlogs.
It would even allow to pass options to improve the compression.  For 
instance with compressformat="gzip -9" to improve compression with gzip, 
or compressformat="xz --memlimit=50%" to limit the hog you mentioned.

-- 
Julien ?LIE

??If I don't document something, it's usually either for a good reason,
   or a bad reason.?? (Larry Wall)


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

Message: 2
Date: Thu, 8 Feb 2024 13:35:47 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: INN2 on a Raspberry Pi 4? | Migrating between instances
        of INN2
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi Paul,

> In thinking about some info I read on how to send articles from
> one server to another. If I want my new server to use the same
> domain name as my old server etc. (what shows in the path) is
> there anyway to transfer articles over from one system to the
> other like that?

I think your use case is OK.  I've not tested but normally, if both your 
old and new servers have the same pathhost value in inn.conf, this value 
is added to the Path header field of articles present in your old 
server, and won't be added again by your new server when feeding 
articles via innxmit.  Articles will be accepted.

See Christoph's answer and detailed instructions here:
   https://www.eyrie.org/~eagle/faqs/inn.html#S6.4

-- 
Julien ?LIE

??Un accus? est cuit quand son avocat n'est pas cru.?? (Pierre Dac)


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

Message: 3
Date: Thu, 8 Feb 2024 13:53:51 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: INN2 on a Raspberry Pi 4? | Migrating between instances
        of INN2
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Adding to my previous message:

> If you think adding native support for xz compression would be useful, 
> the program could be searched for in m4/compress.m4 and, if you build 
> INN with the --with-log-compress=xz flag, it would normally do the trick 
> (not personally tested though).
> Wouldn't it correspond to your local change? (if that's the case, such a 
> change could easily be merged upstream, and usable for your needs as 
> well as other people's needs)
> 
> BTW, I see that this --with-log-compress configure flag is not 
> documented (it is only mentioned in the output of "./configure --help").
> I'll mention it in the relevant manual pages (at least INSTALL, newslog, 
> news.daily and scanlogs).? Current supported methods are gzip, bzip2, 
> compress and cat (meaning no compression at all).

Wouldn't it be enough to just document that you could add in pathetc a 
file named innshellvars.local, executable, containing:

LOG_COMPRESS='/usr/bin/xz'
Z='.xz'


Doesn't the log compression feature with xz work out of the box with 
just that change?

-- 
Julien ?LIE

??Vina bibant homines, animantia cetera fontes.??


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

Message: 4
Date: Thu, 8 Feb 2024 09:15:28 -0600
From: Jesse Rehmer <[email protected]>
To: [email protected]
Subject: Re: INN2 on a Raspberry Pi 4? | Migrating between instances
        of INN2
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 2/8/24 6:35 AM, Julien ?LIE wrote:
> Hi Paul,
> 
>> In thinking about some info I read on how to send articles from
>> one server to another. If I want my new server to use the same
>> domain name as my old server etc. (what shows in the path) is
>> there anyway to transfer articles over from one system to the
>> other like that?
> 
> I think your use case is OK.? I've not tested but normally, if both your 
> old and new servers have the same pathhost value in inn.conf, this value 
> is added to the Path header field of articles present in your old 
> server, and won't be added again by your new server when feeding 
> articles via innxmit.? Articles will be accepted.
> 
> See Christoph's answer and detailed instructions here:
>  ? https://www.eyrie.org/~eagle/faqs/inn.html#S6.4
> 

I can confirm when both hosts have the same pathhost value it will not 
cause any issues, and it does not add a duplicate value.


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

Subject: Digest Footer

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


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

End of inn-workers Digest, Vol 158, Issue 3
*******************************************

Reply via email to