As of the the version 2.9.1 of the IRC server, a client can see all the KILLs occuring on the network by joining the &kills channel. There are various reasons which can trigger a KILL, and the notice sent is the only way to find it.
This document assumes that you already have knowledge of the IRC protocol and that you understand it.
Field short description:
In this example, we can follow the path took by the KILL to reach us:
This is commonly known as a Fake Prefix error condition. nickname has been introduced by server1 but server2 is sending data claiming it comes from nickname (which is impossible since nickname is behind server1 and not behind server2).
Both server1 and server2 are local connections.
server2 is a new server being introduced on the network, but its name is currently being used by another client as a nickname (this client was introduced by server1). This is a Server/nick collision.
The nickname being killed is being introduced by server2 and is supposed to be a client using server1. It is impossible because server1 is not behind server2.
server is propagating an illegal nickname change for nickname!user@hostname.
This is a Nick/Server collision, the local connection is a server which introduced a nickname using the same name as a server behind server1.
This is a ``classic'' nickname collision. The nickname being killed was known from server1 but server2 introduced it again. user2@host2 identifies the new user which was being introduced, and user1@host1 the user which got collided.
This is a ``nickname change'' collision. Both nick1 and nick2 are registered clients. The server issuing the kill does so because nick2 tried to change its name to nick1 (which is already taken).
In theory this shouldn't happen. However, large networks are commonly affected by ``lag'' (delays) which makes this kind of situation possible.
Christophe Kalt <email@example.com>
$Id: kills.html,v 1.5 2000/05/03 16:13:03 kalt Exp $