[IRCServices] RE: IRCServices Digest, Vol 18, Issue 4
chris at unreal-irc.net
chris at unreal-irc.net
Tue Jun 8 07:21:54 PDT 2004
When a user gets akilled due to session limiting I do not expect services to
tell me about it every time the user attempts to reconnect.
Unfortunately, FAQ F9 does not address this.
----
Message: 2
Date: Mon, 7 Jun 2004 19:05:22 +0100
From: <chris at unreal-irc.net>
Subject: [IRCServices] FW: AKill
To: <ircservices at ircservices.za.net>
Message-ID: <200406071808.i57I8SPt015647 at smtp-loh04.proxy.aol.com>
Content-Type: text/plain; charset="us-ascii"
Any akill added on our network results in a massive flood of notices when
the user then attempts to rejoin.
In older versions of services, when an akill was added and the user
attempted to rejoin, we got one notice telling us the user had been akilled
then nothing more. How on earth do we stop the flooding of services with
all these notices each time a user tries to rejoin and gets akilled?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
../attachments/20040607/3ee
0a1cd/attachment-0001.html
------------------------------
Message: 3
Date: Tue, 08 Jun 2004 09:55:01 JST
From: achurch at achurch.org (Andrew Church)
Subject: Re: [IRCServices] FW: AKill
To: ircservices at ircservices.za.net
Message-ID: <40c50ec2.27600 at achurch.org>
Content-Type: text/plain; charset=ISO-2022-JP
RTFM (FAQ F.9), and don't use HTML when posting to the list.
--Andrew Church
achurch at achurch.org
http://achurch.org/
>This is a multi-part message in MIME format.
>
>--===============1162681352==
>Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_0129_01C44CC2.63AC2910"
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_0129_01C44CC2.63AC2910
>Content-Type: text/plain;
> charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>
>Any akill added on our network results in a massive flood of notices when
>the user then attempts to rejoin.
>
>
>
>In older versions of services, when an akill was added and the user
>attempted to rejoin, we got one notice telling us the user had been akilled
>then nothing more. How on earth do we stop the flooding of services with
>all these notices each time a user tries to rejoin and gets akilled?
>
>
>------=_NextPart_000_0129_01C44CC2.63AC2910
>Content-Type: text/html;
> charset="us-ascii"
>Content-Transfer-Encoding: quoted-printable
>
><html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
>xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
>xmlns=3D"http://www.w3.org/TR/REC-html40">
>
><head>
><meta http-equiv=3DContent-Type content=3D"text/html; =
>charset=3Dus-ascii">
><meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
><style>
><!--
> /* Style Definitions */
> p.MsoNormal, li.MsoNormal, div.MsoNormal
> {margin:0cm;
> margin-bottom:.0001pt;
> font-size:12.0pt;
> font-family:"Times New Roman";}
>a:link, span.MsoHyperlink
> {color:blue;
> text-decoration:underline;}
>a:visited, span.MsoHyperlinkFollowed
> {color:purple;
> text-decoration:underline;}
>span.EmailStyle17
> {mso-style-type:personal;
> font-family:Arial;
> color:windowtext;}
>span.EmailStyle18
> {mso-style-type:personal-reply;
> font-family:Arial;
> color:navy;}
>@page Section1
> {size:595.3pt 841.9pt;
> margin:72.0pt 90.0pt 72.0pt 90.0pt;}
>div.Section1
> {page:Section1;}
>-->
></style>
>
></head>
>
><body lang=3DEN-GB link=3Dblue vlink=3Dpurple>
>
><div class=3DSection1>
>
><p class=3DMsoNormal><font size=3D2 face=3DArial><span =
>style=3D'font-size:10.0pt;
>font-family:Arial'>Any akill added on our network results in a massive =
>flood of
>notices when the user then attempts to =
>rejoin.<o:p></o:p></span></font></p>
>
><p class=3DMsoNormal><font size=3D2 face=3DArial><span =
>style=3D'font-size:10.0pt;
>font-family:Arial'><o:p> </o:p></span></font></p>
>
><p class=3DMsoNormal><font size=3D2 face=3DArial><span =
>style=3D'font-size:10.0pt;
>font-family:Arial'>In older versions of services, when an akill was =
>added and
>the user attempted to rejoin, we got one notice telling us the user had =
>been akilled
>then nothing more. How on earth do we stop the flooding of =
>services with
>all these notices each time a user tries to rejoin and gets =
>akilled?<o:p></o:p></span></font></p>
>
></div>
>
></body>
>
></html>
>
>------=_NextPart_000_0129_01C44CC2.63AC2910--
>
>
>
>
>--===============1162681352==
>Content-Type: text/plain; charset="us-ascii"
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices
>
>--===============1162681352==--
>
>
>
------------------------------
Message: 4
Date: Tue, 8 Jun 2004 11:02:24 +1000
From: "Robin Burchell" <Robin.Burchell at oxley.nsw.edu.au>
Subject: Re: [IRCServices] Weird startup thing
To: <ircservices at ircservices.za.net>
Message-ID:
<61210DEC11A6624EBE04311BDB604A140C0B43 at oxleyserver.oxley.nsw.edu.au>
Content-Type: text/plain; charset="UTF-8"
That's what throws me--
We are using 5.0.30 vanilla-- yet it reported 1.0.1a!?!
Craig, cmon its me here, w00t! I didnt even USE ircservices till you told me
about it
The problem seems to have resolved itself-- we tried ./ircservices -debug
and the problem vanished...
Will keep you all posted.
Robin Burchell [w00t]
Administrator, irc.netronet.org
------------------------------
Message: 5
Date: Tue, 08 Jun 2004 09:58:18 JST
From: achurch at achurch.org (Andrew Church)
Subject: [IRCServices] Services 5.0.32 released
To: services <ircservices at ircservices.za.net>
Message-ID: <40c50fa8.27635 at achurch.org>
Content-Type: text/plain; charset=ISO-2022-JP
Services 5.0.32 has been released, and can be downloaded from:
ftp://ftp.esper.net/ircservices/ (Western USA)
6269c6f7a6f73b577f23df7e84612c31 ircservices-5.0.32.tar.gz
d1677618884bdc517933ffbd95d32b3a ircservices-5.0.32.diff.gz
ded4e8e85224be005789e969662805b0 ircservices-5.0.32-1.i386.rpm
171a7badeebb4e6b617a5580e43dc38e ircservices_5.0.32-1_i386.deb
ftp.ircservices.za.net and the other mirrors should have it shortly.
This release includes updated support for the most recent versions of
the Unreal and Bahamut IRC servers, in addition to the usual bug fixes and
a minor internal change in the ChanServ module interface.
PLEASE NOTE that, as announced earlier, Bahamut versions earlier than
1.8.0 are no longer supported as of this release of Services. If you are
using Bahamut, you MUST upgrade all of your servers to Bahamut 1.8.0 at the
same time you upgrade Services. I apologize for the inconvenience.
Changes in version 5.0.32
-------------------------
2004/06/07 Updated Unreal protocol module for Unreal 3.2.1.
2004/05/24 get_access() (which returns a user's access level on a
channel) is now exported by the chanserv/main module.
2004/05/18 -z (insecure) users can no longer enter channels locked to
+z on Unreal. Reported by Dionisios K.
<vonitsa_net at yahoo.gr>
2004/05/14 Fixed failure to clear ban exceptions on autokick.
Reported by Eric Murphy <emurphy at sporked.us>
2004/05/12 Updated Bahamut protocol module for Bahamut 1.8.0. Support
for 1.4.x has been removed.
2004/05/07 Fixed errors in OperServ SESSIONS and EXCEPTIONS help text.
Reported by Elijah <admin at nevernet.net>
2004/05/04 Fixed harmless compilation warning in database/version4
module. Reported by Craig McLure <Craig at chatspike.net>
--Andrew Church
achurch at achurch.org
http://achurch.org/
------------------------------
_______________________________________________
IRCServices mailing list
IRCServices at ircservices.za.net
http://www.ircservices.za.net/mailman/listinfo/ircservices
End of IRCServices Digest, Vol 18, Issue 4
******************************************