short answer: your nickserv on gnuworld is expected to act as a server not an irc client, even tho it is normally seen to appear to be a normal irc client from the rest of the irc server's on the network.
to help clarify what Perry wrote: imagine a network with at least 3 servers A, B, and C (unlike your 2 servers), lets make A the clients server, B a hub, and C your gnuworld/nickserv, when you issue the kill from C for a client on A, A will still send the returning kill you are seeing, however C will not see that returning kill because B already knows that numeric nick doesn't exist. (because B had already processed the kill message from C), This is normal for servers because all server's immediately remove the client from there "record" of currently valid irc client connections, if my understanding is correct, that returning ghost clean up kill is only ever generated by the server the client is/was actually on, and a server does not pass on kill's for invalid clients (unless by some weird bad luck in this example B somehow managed to pass the original kill onto A without processing it). the quit message you see as an oper is due to the client <-> server protocol. a kill message is only valid from the client to the server (client -> server) not the reverse direction (client <- server), quit is the only valid message for the server to notify a client of when other clients disconnect (which is also why quit is used for netsplits). PS: this is merely my understanding after following this mail list for a few years. -- xplora is wakco (Richard T Smith) yeehaa, doggy... b44w00f Technician, Media Design School Ltd. [EMAIL PROTECTED], Official CService Admin, Undernet Channel Service Committee, Undernet IRC Network. Note: Unless stated this email is from my own thoughts and opinions and does not represent Undernet, CService, or Media Design School Ltd. > From: <[EMAIL PROTECTED]> > Date: Wed, 26 Dec 2001 00:27:54 +0000 (GMT) > To: <[EMAIL PROTECTED]> > Subject: Re: [Coder-Com] Server kill question > > On Wed, 26 Dec 2001, Perry Lorier wrote: >> You should never see a Quit back. Kill's are kills they remove the >> client immediately. However what ircu's trying to prevent is a quit and >> a kill crossing and ending up with a desync, so it kill's the user again >> from the local server, knowing that the kill won't get passed on if >> it doesn't match a user, but if it does then it will clear out any >> possible desync. > > But when, for example, an oper kills a remote user, the server that owns > that user will then disconnect him and issue a QUIT, precisly so that all > other servers know that user has been disconnected...? >
