[IRCServices Coding] 5.0a24 - Problem with szline

[Andrew Church]

     I'm planning to (before the beta release) rework the expiration system
to take care of this, so it won't get fixed immediately.  For now, just do
an "SLINE DEL *@xx.xx.xx.xx" (or alternatively UPDATE, which checks for
expiration as well) if you run into this.

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

>When an szline has been set and has expired allowing the user to reconnect, 
>it is impossible to set a new szline on the same IP address unless another  
>szline command (list or del) is issued, i.e.:
>
>*** Global -- from OperServ: Mark added an SZLINE for xx.xx.xx.xx(expires 
>in 1 minute)
>*** Notice -- Client exiting: xxxxx (xxxx at xxxxx) [Z:lined (Z-lined: test)]
>-OperServ- xx.xx.xx.xx already exists on SZLINE list.
>[expected operation]
>*** Expiring Global Z:Line (*@xx.xx.xx.xx) made by Mark (Reason: Z-lined: 
>test) set 26 seconds ago
>-OperServ- xx.xx.xx.xx already exists on SZLINE list.
>*** Notice -- Client connecting on port 6667: xxxxx (xxxx at xxxxxx) 
>-OperServ- xx.xx.xx.xx already exists on SZLINE list.
>[unexpected operation]
>
>(xxx for privacy)
>
>An szline list produces an empty list (assuming no other szlines exists) so 
>services has in one way removed the entry, but it appears to retain the 
>entry in it's checking for multiple add calls until the next szline command 
>resets it. 
>
>This problem may exist in all sline commands, but I have only tested szline 
>so far. 
>
>-- 
>Mark.
>
>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices-coding