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. INN and local cancel messages (Chris Knipe)
2. Re: INN and local cancel messages (Russ Allbery)
3. Re: INN and local cancel messages (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Wed, 3 Feb 2016 17:00:19 +0200
From: Chris Knipe <[email protected]>
To: [email protected]
Subject: INN and local cancel messages
Message-ID:
<CA+4TWFv=k0qx7o2svr887gkqjdozdravmq3hc1xf8vymvx-...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
If I cancel a message locally on INN (innctld cancel <messageid>),
How is the message (and more importantly, space) in a CYCBUFF re-used? Is
it reused at all, or not?
>From what I can gather, the actual message file is removed in a timehash
store, and I suspect the same would hold true for timecaf and tradspool
(i.e. the storage space is return to the OS), but from the documentation I
am unable to determine whether the space will be re-used for a different
(new) article when I use a CYCBUFF (i.e. storage space return to CYCBUFF).
Many thnx.
--
Regards,
Chris Knipe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/inn-workers/attachments/20160203/8f598744/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 03 Feb 2016 12:34:39 -0800
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: INN and local cancel messages
Message-ID: <[email protected]>
Content-Type: text/plain
Chris Knipe <[email protected]> writes:
> If I cancel a message locally on INN (innctld cancel <messageid>),
> How is the message (and more importantly, space) in a CYCBUFF re-used? Is
> it reused at all, or not?
It's not. The cycbuff doesn't go back and use space until it rolls over
and the whole cycbuff starts being reused.
> From what I can gather, the actual message file is removed in a timehash
> store, and I suspect the same would hold true for timecaf and tradspool
> (i.e. the storage space is return to the OS),
Correct.
> but from the documentation I am unable to determine whether the space
> will be re-used for a different (new) article when I use a CYCBUFF
> (i.e. storage space return to CYCBUFF).
Nope. It's exactly the same from a storage perspective as if you hadn't
cancelled the article. The only thing that ctlinnd cancel does is remove
the article from overview and hide it from clients.
--
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: 3
Date: Wed, 3 Feb 2016 21:50:41 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: INN and local cancel messages
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi,
>> From what I can gather, the actual message file is removed in a timehash
>> store, and I suspect the same would hold true for timecaf and tradspool
>> (i.e. the storage space is return to the OS),
>
> Correct.
Just a precision as for timecaf: a comment in the source code mentions
that no space is returned to the OS at the time of the cancel. It only
happens when expire is run, and treats the CAF file.
Maybe that fact could be useful to Chris.
--
Julien ?LIE
? C'est tout un art que de parvenir ? couper un g?teau de telle
sorte que chacun croit en avoir eu la plus grosse part. ?
------------------------------
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
End of inn-workers Digest, Vol 81, Issue 1
******************************************
