From Newsgroup: news.admin.misc

Hi,

I got no responses in news.software.nntp, so I'll ask here. Here's the original message for context:

Message-ID: <5dcbedb5-81e3-4ba1-a218-ac52c626cb05-aw@news.chmurka.net>

In short: anyone else experienced "expire" process that's run from
news.daily to hang sometimes? It doesn't do anything, just waits on a
socket, and it leaves the server throttled with "400 Expiring process
<pid>" message for hours.

inn 2.7.0
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: news.admin.misc

aw@somewhere.invalid (Adam W.) writes:

Hi,

Why do you have five Cancel-Lock hashes in your headers? One from your
client, one from your server, where are the rest coming from?
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: news.admin.misc

Hi Schlomo,

Why do you have five Cancel-Lock hashes in your headers? One from your client, one from your server, where are the rest coming from?

I guess the first sha1 was set by tin, the second sha1 with its related
sha256 were set by INN for the newsmaster (allowing him to generate an appropriate Cancel-Key), and the third sha1 with its related sha256 were
set by INN for the "arnold" user (if the same "arnold" account sends a
cancel, INN will add an appropriate Cancel-Key that only "arnold" could trigger, independently of the news client used which could be different
than tin).
--
Julien |eLIE

-2-aEx nihilo nihil.-a-+ (Perse)

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: news.admin.misc

Julien +LIE <iulius@nom-de-mon-site.com.invalid> wrote:

I guess the first sha1 was set by tin, the second sha1 with its related sha256 were set by INN for the newsmaster (allowing him to generate an appropriate Cancel-Key), and the third sha1 with its related sha256 were
set by INN for the "arnold" user (if the same "arnold" account sends a cancel, INN will add an appropriate Cancel-Key that only "arnold" could trigger, independently of the news client used which could be different
than tin).

Exactly. Probably an overkill, but I had Cancel-Lock set up in tin before
inn supported it, and it stayed this way.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: news.admin.misc

Julien |eLIE <iulius@nom-de-mon-site.com.invalid> writes:

Hi Schlomo,

Why do you have five Cancel-Lock hashes in your headers? One from your
client, one from your server, where are the rest coming from?

I guess the first sha1 was set by tin, the second sha1 with its
related sha256 were set by INN for the newsmaster (allowing him to
generate an appropriate Cancel-Key), and the third sha1 with its
related sha256 were set by INN for the "arnold" user (if the same
"arnold" account sends a cancel, INN will add an appropriate
Cancel-Key that only "arnold" could trigger, independently of the news
client used which could be different than tin).

Got it, thanks.
--- Synchronet 3.21d-Linux NewsLink 1.2