software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/2000/000427.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Services
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services&In-Reply-To=20000106213639.16411.qmail%40hotmail.com">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="000420.html">
  11    <LINK REL="Next"  HREF="000421.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Services</H1>
  15     <B>Chris Knipe</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services&In-Reply-To=20000106213639.16411.qmail%40hotmail.com"
  17        TITLE="[IRCServices] Services">cgknipe at mweb.co.za
  18        </A><BR>
  19     <I>Sun Jan  9 05:38:11 PST 2000</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000420.html">[IRCServices] Services
  22 </A></li>
  23         <LI>Next message: <A HREF="000421.html">[IRCServices] ChanServ KICK command(?)
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#427">[ date ]</a>
  27               <a href="thread.html#427">[ thread ]</a>
  28               <a href="subject.html#427">[ subject ]</a>
  29               <a href="author.html#427">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>On Thu, 6 Jan 2000, Angel of Death wrote:
  35
  36 Hi ...
  37
  38 I won't stay long on this, it might not even be a good solution, but here
  39 goes...
  40
  41 Crontab, *CAN* do what is needed...
  42
  43 &gt;&gt;<i>I don't think everyone is understanding the situation presented here. Say
  44 </I>&gt;&gt;<i>you have Services running on server A. Services links to server B, not an
  45 </I>&gt;&gt;<i>ircd on the same box (A). Server B crashes. Now Services are no where
  46 </I>&gt;&gt;<i>because the .conf file only has one server (B) to link to. This is
  47 </I>&gt;&gt;<i>correctable if a person with access to server A is around to edit the .conf
  48 </I>&gt;&gt;<i>file, but the situation is that, that person is not around. So the asked
  49 </I>&gt;&gt;<i>for solution is to have multiple S:lines in the .conf file that Services
  50 </I>&gt;&gt;<i>would attempt to link to in the event the primary is down. Setting up a
  51 </I>&gt;&gt;<i>crontab to restart the ircd on server B is moot because server B is dead.
  52 </I>&gt;&gt;<i>This is what I gathered from Angel's emails. Correct me if I'm wrong.
  53 </I>
  54 &gt;<i>From the Services Documentation:
  55 </I>
  56      Normally, Services can be run simply by invoking the &quot;services&quot;
  57 executable.  Services will then use the defaults specified in the
  58 services.conf file, and connect to the specified uplink server.
  59 Alternatively, any of the following command-line options can be specified
  60 to change the default values:
  61
  62         -remote server[:port]   Connect to the specified server
  63         -local host  -or-       Connect from the specified address (e.g.
  64                [host]:[port]        for multihomed servers)
  65         -name servername        Our server name (e.g. services.some.net)
  66         -desc string            Description of us (e.g. SomeNet Services)
  67         -user username          Username for Services' nicks (e.g. services)
  68         -host hostname          Hostname for Services' nicks (e.g. esper.net)
  69         -dir directory          Directory containing Services' data files
  70                                     (e.g. /usr/local/lib/services)
  71         -log filename           Services log filename (e.g. services.log)
  72         -update secs            How often to update databases (in seconds)
  73         -expire secs            How often to check for nick/channel
  74                                     expiration (in seconds)
  75
  76 ---
  77
  78 Now with an rather interesting sh / bash script, you will be able to ping
  79 or traceroute the server to where your services are supposed to link to
  80 (most shell providers allow the use of ping).  From the output, you can
  81 easily grep the ping statistics...
  82
  83 &gt;<i>From standard Linux (output returned by ping might vary from OS to OS),
  84 </I>issuing something like the command below, will give you an good idea of the
  85 current network performance to any remote server where services could or
  86 shoud be linking to...
  87
  88    ping -c 50 &lt;host name&gt; | grep received | cut -c 43-70
  89    0% packet loss
  90
  91 &gt;<i>From the ammount of packet loss returned, you can then reliably decide
  92 </I>where to link to, or what other actions to take. (Hence if you have the
  93 access, you can even change routing tables - would it be neccessary).
  94
  95 Should 100% packet loss be returned, that would obviously mean the server
  96 is dead, now you can re-invoke services with the -remote parameter, linking
  97 your services to the server specified.
  98
  99 The matter of C/N lines in this case, would depend on the remote server
 100 where services is linking to.
 101
 102 Mind you, this type of configuration can even be used to &quot;re-route&quot;
 103 services should lag become an problem.
 104
 105 Regards
 106 Chris Knipe
 107 Cel: (083) 430 8151
 108 Freelance Internet Developer, Consultant, Administrator &amp; Speaker
 109
 110
 111 ---------------------------------------------------------------
 112 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
 113 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
 114
 115 </PRE>
 116
 117 <!--endarticle-->
 118     <HR>
 119     <P><UL>
 120         <!--threads-->
 121         <LI>Previous message: <A HREF="000420.html">[IRCServices] Services
 122 </A></li>
 123         <LI>Next message: <A HREF="000421.html">[IRCServices] ChanServ KICK command(?)
 124 </A></li>
 125          <LI> <B>Messages sorted by:</B>
 126               <a href="date.html#427">[ date ]</a>
 127               <a href="thread.html#427">[ thread ]</a>
 128               <a href="subject.html#427">[ subject ]</a>
 129               <a href="author.html#427">[ author ]</a>
 130          </LI>
 131        </UL>
 132
 133 </body></html>