head 1.5; access; symbols; locks; strict; comment @# @; 1.5 date 2000.05.03.16.13.03; author kalt; state Exp; branches; next 1.4; 1.4 date 97.09.29.12.05.57; author kalt; state Exp; branches; next 1.3; 1.3 date 97.06.12.13.01.21; author kalt; state Exp; branches; next 1.2; 1.2 date 97.04.14.20.17.05; author kalt; state Exp; branches; next 1.1; 1.1 date 97.04.14.20.12.09; author kalt; state Exp; branches; next ; desc @&KILLS explanation @ 1.5 log @moved to irc.org, fixed links @ text @IRC.org / IRC 2.9 & 2.10 - &KILLS 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.

General notice format

:local.server.name NOTICE &KILLS :Received KILL message for <target>. From <source> Path: <kill path> (<description>)

Field short description:

Understanding server kills

You will find all description formats below with a short explanation. Unless otherwise noted, the point of view of the following is the server issuing the kill.

Christophe Kalt <kalt@@stealth.net>

$Id: kills.html,v 1.4 1997/09/29 12:05:57 kalt Exp kalt $
@ 1.4 log @ajout du paragraphe "nickname change collision". @ text @d1 4 a4 2 IRC 2.9 - &KILLS d14 1 a14 1

General notice format

d59 1 a59 1

Understanding server kills

d123 1 a123 1
$Id: kills.html,v 1.3 1997/06/12 13:01:21 kalt Exp kalt $
d125 1 a125 1 @ 1.3 log @fixed typo (from Alain Nissen ) @ text @a2 4 This document was last modified on

d74 1 a74 1

d80 1 a80 1

d86 1 a86 1

d91 1 a91 1

d96 1 a96 1

d98 2 a99 2 This is a ``classic'' nickname collision. The nickname being killed was known from server1 but d103 11 a113 4

The new user introduced can either be a new client on the network, or an old one trying to change nickname at the wrong time. d121 1 a121 1

$Id: kills.html,v 1.2 1997/04/14 20:17:05 kalt Exp kalt $
@ 1.2 log @added $Id$ @ text @d101 1 a101 1
  • (user1@@host2)server1 <- (user2@@host2)server2

    d118 1 a118 1

    $Id$
    d120 1 a120 1 @ 1.1 log @Initial revision @ text @d118 2 @