software/RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000669.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> AW: [IRCServices] Faster AKILL Processing...
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%5D%20Faster%20AKILL%20Processing...&In-Reply-To=l0313030fb59b979b5e6d%40%5B10.38.239.105%5D">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="000667.html">
  11    <LINK REL="Next"  HREF="000670.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>AW: [IRCServices] Faster AKILL Processing...</H1>
  15     <B>Yusuf Iskenderoglu</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=AW%3A%20%5BIRCServices%5D%20Faster%20AKILL%20Processing...&In-Reply-To=l0313030fb59b979b5e6d%40%5B10.38.239.105%5D"
  17        TITLE="AW: [IRCServices] Faster AKILL Processing...">uhc0 at rz.uni-karlsruhe.de
  18        </A><BR>
  19     <I>Wed Jul 19 14:00:39 PDT 2000</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000667.html">AW: [IRCServices] Faster AKILL Processing...
  22 </A></li>
  23         <LI>Next message: <A HREF="000670.html">AW: [IRCServices] Faster AKILL Processing...
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#669">[ date ]</a>
  27               <a href="thread.html#669">[ thread ]</a>
  28               <a href="subject.html#669">[ subject ]</a>
  29               <a href="author.html#669">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>
  35 Hi again;
  36
  37 I've merged my thoughts about this topic and came to the following option,
  38 which probably decrease the load on services.
  39
  40 You could set up another set of services, which is started in -skeleton, leading to
  41 everything but OperServ disabled, and advisable is not to use confusing nicknames
  42 for the known part of services. That OperServ can be used to place akills, and manage akills,
  43 and remove akills etc, without taking any time from the real services which still continue working.
  44
  45 I think your opers should not be that much unhappy having to identify to let's say ServBot in order to
  46 use the *new* AkillServ.
  47
  48 Regards,
  49
  50 ---------------------------------
  51 Yusuf Iskenderoglu
  52 eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">uhc0 at rz.uni-karlsruhe.de</A>
  53 eMail - <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">s_iskend at ira.uka.de</A>
  54 ICQ : 20587464 \ TimeMr14C
  55 ---------------------------------
  56
  57 &gt;<i> -----Ursprungliche Nachricht-----
  58 </I>&gt;<i> Von: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at ender.shadowfire.org</A>
  59 </I>&gt;<i> [mailto:<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">owner-ircservices at ender.shadowfire.org</A>]Im Auftrag von Jonathan
  60 </I>&gt;<i> Morton
  61 </I>&gt;<i> Gesendet: Wednesday, July 19, 2000 7:56 PM
  62 </I>&gt;<i> An: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">ircservices at delirious.shadowfire.org</A>
  63 </I>&gt;<i> Betreff: Re: AW: [IRCServices] Faster AKILL Processing...
  64 </I>&gt;<i>
  65 </I>&gt;<i>
  66 </I>&gt;<i> &gt;Therefore it is in my opinion, adviseable to let services manage akills,
  67 </I>&gt;<i> &gt;instead of any server on a network,
  68 </I>&gt;<i> &gt;that even do not need to.
  69 </I>&gt;<i>
  70 </I>&gt;<i> I thought the argument was to distribute the processing across
  71 </I>&gt;<i> the servers,
  72 </I>&gt;<i> rather than having the _entire_ load on Services.  If the services machine
  73 </I>&gt;<i> is more powerful than all the others put together, and network latency is
  74 </I>&gt;<i> low, then it makes great sense to match them all on Services, then issue
  75 </I>&gt;<i> /kill and /kline from there.  Also, _if_ troublemakers tend to come back
  76 </I>&gt;<i> infrequently compared to the reboot frequency, then this is an acceptable
  77 </I>&gt;<i> solution.  However, I suspect that neither of these assumptions holds true
  78 </I>&gt;<i> for many networks.
  79 </I>&gt;<i>
  80 </I>&gt;<i> The solution of keeping every server updated with a K-line list has it's
  81 </I>&gt;<i> own problems, though.  With a large list of AKILLs and a large number of
  82 </I>&gt;<i> servers, the traffic caused by the updates could become significant and
  83 </I>&gt;<i> lead to further problems.  However this is exactly the situation where the
  84 </I>&gt;<i> distribution of processing would be most useful.  Throttling
  85 </I>&gt;<i> would probably
  86 </I>&gt;<i> be the best solution to the &quot;flooding&quot; problem, using a 'trickle'
  87 </I>&gt;<i> of /kline
  88 </I>&gt;<i> commands to update the remote server(s), possibly even with a delay to
  89 </I>&gt;<i> allow the usual &quot;recovering from netsplit&quot; traffic to subside.  This
  90 </I>&gt;<i> completely frees up Services from the usual burden of matching AKILLs and
  91 </I>&gt;<i> allows it to concentrate on it's other tasks in a more &quot;managerial&quot; role.
  92 </I>&gt;<i>
  93 </I>&gt;<i> Again, this would best be configurable as an admin option, as with all
  94 </I>&gt;<i> major behavioural changes.
  95 </I>&gt;<i>
  96 </I>&gt;<i> --------------------------------------------------------------
  97 </I>&gt;<i> from:     Jonathan &quot;Chromatix&quot; Morton
  98 </I>&gt;<i> mail:     <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">chromi at cyberspace.org</A>  (not for attachments)
  99 </I>&gt;<i> uni-mail: <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">j.d.morton at lancaster.ac.uk</A>
 100 </I>&gt;<i>
 101 </I>&gt;<i> The key to knowledge is not to rely on people to teach you it.
 102 </I>&gt;<i>
 103 </I>&gt;<i> Get VNC Server for Macintosh from &lt;A  HREF=&quot;<A HREF="http://chromatix.autistics.org/vnc/&quot;">http://chromatix.autistics.org/vnc/&quot;</A>&gt;<A HREF="http://chromatix.autistics.org/vnc/&lt;/A">http://chromatix.autistics.org/vnc/&lt;/A</A>&gt;
 104 </I>&gt;<i>
 105 </I>&gt;<i> -----BEGIN GEEK CODE BLOCK-----
 106 </I>&gt;<i> Version 3.12
 107 </I>&gt;<i> GCS$/E/S dpu(!) s:- a19 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
 108 </I>&gt;<i> PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r- y+
 109 </I>&gt;<i> -----END GEEK CODE BLOCK-----
 110 </I>&gt;<i>
 111 </I>&gt;<i>
 112 </I>&gt;<i>
 113 </I>&gt;<i> ---------------------------------------------------------------
 114 </I>&gt;<i> To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
 115 </I>&gt;<i> with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
 116 </I>&gt;<i>
 117 </I>
 118
 119 ---------------------------------------------------------------
 120 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
 121 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
 122
 123
 124 </PRE>
 125
 126 <!--endarticle-->
 127     <HR>
 128     <P><UL>
 129         <!--threads-->
 130         <LI>Previous message: <A HREF="000667.html">AW: [IRCServices] Faster AKILL Processing...
 131 </A></li>
 132         <LI>Next message: <A HREF="000670.html">AW: [IRCServices] Faster AKILL Processing...
 133 </A></li>
 134          <LI> <B>Messages sorted by:</B>
 135               <a href="date.html#669">[ date ]</a>
 136               <a href="thread.html#669">[ thread ]</a>
 137               <a href="subject.html#669">[ subject ]</a>
 138               <a href="author.html#669">[ author ]</a>
 139          </LI>
 140        </UL>
 141
 142 </body></html>