Alas, I already did this. As can be seen in the SERVER out string in the
logs I mailed, the connections are set to around 200 odd. The standard for
gnuworld is AAz which is around 50 somewhere.
Also, I should point out that evern with the 50 set, it still falls over
with more than 4 or 5 clients.
OK.. have been tearing my hair out for a while now trying to figure out
why this happens...
Basically, I am writing a NickServ type GNUworld module, to protect
peoples registered nicks. A nice easy way to prevent anyone from changing
to that nick after the client has been killed, is to 'jupe' tha
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
On Tue, 25 Dec 2001, nighty wrote:
> Hello,
> just my two cents ...
> have you tried ... A5AAA D ABAAD :kill reason ?
> i mean .. it "looked" like weird to me that you make the /kill issued by the server
>(two first chars of numeric)
> rather than by the NickServ client.
The problem is that when
Hi
Am looking for a bit of advice regarding servers killing remote clients.
Specifically, I am writing a NickServ type module for GNUworld and need to
kill clients if they exceed their time without authing. The problem is
that when I send the D token, the remote server bounces it back to me
instea
