[IRCServices Coding] 5.0a24 and +S clients

Andrew Church achurch at achurch.org
Wed Mar 13 15:24:19 PST 2002


     Okay, this should be fixed now.

  --Andrew Church
    achurch at achurch.org
    http://achurch.org/

>     It looks like this is because the other program is sending a message
>not understood by Services (whichever message corresponds to the "n" token
>in the log below, I haven't looked it up).  It's probably SVSMODE or some
>such and just needs to have a handler added--I'll take a look.
>
>  --Andrew Church
>    achurch at achurch.org
>    http://achurch.org/
>
>>This is much better in 5.0a24 and if a +S client is on the network when 
>>Services joins, it correctly ignores the client and does not change it's 
>>modes. :)
>>
>>However, if the +S client joins after services is running, services will 
>>enforce modes against it:
>>
>>In channel:
>>*** StatServ (stats at stats.xxxxx.net) has joined #stats
>>*** stats.xxxxx.net sets mode: +o StatServ
>>*** StatServ sets mode: +a StatServ
>>*** ChanServ sets mode: -ooa StatServ StatServ StatServ
>>
>>In services.log:
>>unknown message from server (:StatServ n StatServ +Sq)
>>
>>Andrew, anything specific I should look for that would help nail this one 
>>down? I am guessing that services misses the /mode +S issued by StatServ, 
>>and the error message in the log suggests this is what is happening. I am 
>>going to check the StatServ startup code now to see exactly what it thinks 
>>it is sending.
>>
>>-- 
>>Mark.
>>
>>
>>------------------------------------------------------------------
>>To unsubscribe or change your subscription options, visit:
>>http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices-coding