Re: inn "expire" process hangs (400 Expiring process <pid>)

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.