1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices] A big problem - services being flooded
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20big%20problem%20-%20services%20being%20flooded&In-Reply-To=">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"001642.html">
11 <LINK REL=
"Next" HREF=
"001650.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices] A big problem - services being flooded
</H1>
16 <A HREF=
"mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20A%20big%20problem%20-%20services%20being%20flooded&In-Reply-To="
17 TITLE=
"[IRCServices] A big problem - services being flooded">achurch at achurch.org
19 <I>Mon Mar
19 15:
42:
01 PST
2001</I>
21 <LI>Previous message:
<A HREF=
"001642.html">[IRCServices] A big problem - services being flooded
23 <LI>Next message:
<A HREF=
"001650.html">[IRCServices] [Long mail] Service won't deop a user
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#1643">[ date ]
</a>
27 <a href=
"thread.html#1643">[ thread ]
</a>
28 <a href=
"subject.html#1643">[ subject ]
</a>
29 <a href=
"author.html#1643">[ author ]
</a>
34 <PRE>><i>I had thought of this while starting the todo discussion, but forgot about it till now.
36 </I>><i>Is there any form of flood protection in services?
38 There is, but I'm not sure it works properly at the moment. One of my
39 goals for
5.0 is to get it working better.
41 ><i>Oh and in case you were wondering, If you keep on identifying once every second,
42 </I>><i>since a line is
110 characters long, it will take you approximately
110 days to fill up
43 </I>><i>1 GB. I know how impossible this is, hence it is not my main concern, so please don't
44 </I>><i>flame on this. My main point is the cluttering of the log file and services lag.
46 </I>><i>For Example. As a friend so happily demostrated for me, he logged on and kept on
47 </I>><i>identifying once or twice every second. Services didn't react, obviously, since there
48 </I>><i>is no flood protection in it.
50 Services won't protect against this; as you yourself point out above, at this
51 rate it would take forever to fill up your hard disk. I do, however, see how this
52 could get to be a problem if
100 clones do it at the same time, so I'll see about
53 disabling logging for users who are already identified.
55 However, the main purpose of ignore is to prevent users lagging Services (by
56 sending commands that take a long time), not to prevent the log filling up your
57 disk space, which you can check for outside of Services using cron and ls, among
58 others. As such, IDENTIFY is insignificant, and things like LIST *a*b*c*d* are
59 more of a concern. I do agree that repeat commands are a problem, but for the
60 time being you should be able to take care of this with ircd flood control.
63 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices">achurch at achurch.org
</A> | New address - please note.
64 <A HREF=
"http://achurch.org/">http://achurch.org/
</A> |
メールアドレスが変わりました。
73 <LI>Previous message:
<A HREF=
"001642.html">[IRCServices] A big problem - services being flooded
75 <LI>Next message:
<A HREF=
"001650.html">[IRCServices] [Long mail] Service won't deop a user
77 <LI> <B>Messages sorted by:
</B>
78 <a href=
"date.html#1643">[ date ]
</a>
79 <a href=
"thread.html#1643">[ thread ]
</a>
80 <a href=
"subject.html#1643">[ subject ]
</a>
81 <a href=
"author.html#1643">[ author ]
</a>