[IRCServices Coding] Re: Akill problem in 5.0.22

[Ballsy]

         Yes, Bahamut will immediately kill users matching an Akill.  It 
won't wait for another client from that host to connect.  My setup of IRC 
Services 5.0.22 and bahamut-1.4.30 is doing it right now.  As alluded to in 
a previous email, however, you may need to commented out EnableExclude in 
the services config to have this work.

Ballsy


At 12:49 PM 18/10/2003, V13 wrote:
>On Saturday 18 October 2003 07:20, Robert F Merrill wrote:
> > Saturn wrote:
> > >Would have been nice if someone had mentioned that (about the
> > >ImmediatelySendAutokill) from the start.  I would say the flag is
> > > misleading in title then, because I (and 8 other people on my staff --
> > > none of us are dummies, either) read that as meaning it will Immediately
> > > send the auto kill... "ImmediatelyUpdateServers" might be more fitting
> > > from an intuitive standpoint, not that I'm suggesting changing the name,
> > > but at least the documentation of it could be a bit more explicit IMHO.
> >
> > It DOES immediately send the autokill. You just don't grasp the meaning
> > of sending the autokill.
> > It literally sends an AKILL (or TKL in the case of unreal) message to
> > the servers. At least unreal
> > and bahamut will then scan for matching clients and disconnect them,
> > however not all servers
> > do this.
>
>FYI bahamut doesn't do this. It will only do it whenever a new client that
>matches the akill connects to the server.
>
>i.e. if you set an akill for *.com noone will be disconnected untill a new
>client from *.com gets connected (at that moment, all matching clients will
>be killed). In the mean time, anyone from other domains can connect to the
>server without having any user killed.
>
><<V13>>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices-coding