Proposed patch: cancel channel

Matus "fantomas" Uhlar uhlar at fantomas.sk
Thu Apr 13 20:56:58 UTC 2000


-> > -> > The idea is that for sending local cancels in bulk, the NNTP
-> > -> > (unix-domain) socket is used. The client connects, sends the new
-> > -> > command MODE CANCEL, waits for response (new code 284) and after
-> > -> > that it simply sends all Message-IDs it wants to be cancelled. For
-> > -> > each one it gets a response code 289 for success and 484 for
-> > -> > failure. Other than the command protocol, this works exactly like
-> > -> > "ctlinnd cancel".  On a TCP/IP socket, the MODE CANCEL command is
-> > -> > refused, so only locally installed programs under the news UID can
-> > -> > use it.
-> 
-> > can't this be done already by connecting innd socket ?
-> 
-> ctlinnd cancel, you mean?

i mean "control" socket; shouldn't have big overhead imho

-> Yes, but the advantage of the above protocol
-> over that (apart from the fact that anything that goes through ctlinnd has
-> too much of a setup and teardown overhead since it requires creating
-> temporary sockets)

hmmm can't we just open socket and send X cancel commands directly to innd,
by avoiding ctlinnd ? should I RTFS ?

-> is that down the road we can add a key to incoming.conf that allows
-> remote systems to use MODE CANCEL. And then we're much closer to an
-> effective distributed filtering system that doesn't have the
-> authorization problems that cancels do....

of course, that's what we want...
-- 
 Matus "fantomas" Uhlar, sysadmin at NEXTRA, Slovakia; IRCNET admin of *.sk
 uhlar at fantomas.sk ; http://www.fantomas.sk/ ; http://www.nextra.sk/
 LSD will make your ECS screen display 16.7 million colors



More information about the inn-workers mailing list