fix for spin clone kill timer crash

[irc/evilnet/x3.git] / x3.conf.example

diff --git a/x3.conf.example b/x3.conf.example
index bb4535e942cf23f182926fa4bfbeb4a6ff9092d1..3700d34dd89e59bf9403451d59efeb4861f2aef6 100644 (file)
--- a/x3.conf.example
+++ b/x3.conf.example
@@ -15,7 +15,7 @@
  */
 "uplinks" {
     // This first entry connects to an ircd on teh same server an X3..
-    "Hub" {  // This can be any string, just used here for your conveniance
+    "Hub" {  // This can be any string, just used here for your convenience
         "address"        "127.0.0.1";  // The IP address of the server
         "port"           "8888";       // What TCP port to connect to
         "password"       "laoo,rpe";  // Both of these passwords must match 
@@ -51,13 +51,15 @@
     "key1" "45432"; // Set these key values to the network KEY values you use
     "key2" "76934"; // for host hiding style 2.
     "key3" "98336";
+    "prefix" "AfterNET"; // If you use style 2 then this is the name that is prefixed to hosts.
     "numeric" "51"; // hint: If you get collisions on link, CHANGE THIS.
     /* Type handles some changes in nefarious 1.0 (was 0.5.0)
      * 4 - nefarious 0.4.x and other ircds
-     * 5 - nefarious 1.0.x and higher (Branch Revision)
-     * 6 - nefarious 1.0.x and higher (Trunk Revision)
+     * 5 - nefarious 1.0.x and higher (Obselete)
+     * 6 - nefarious 1.1.0 and higher (Branch Revision)
+     * 7 - nefarious 1.2.0 and higher (Trunk Revsions)
      */
-    "type" "5";
+    "type" "6";
     "host_in_topic" "1"; //Set to 1 if your Nefarious server have the HOST_IN_TOPIC F:line set to TRUE.
     "max_users" "256"; // You can save a little memory by setting this to a lower value.
     "force_n2k" "1"; // Use extended (5-digit) numnick for self, even if 3 are possible.
@@ -248,6 +250,7 @@
         //"ldap_field_email" "mail";
         //// This bit is needed if you want to put ircops into a group:
         //"ldap_oper_group_dn" "cn=Opers,ou=Groups,dc=afternet,dc=org";
+        //"ldap_oper_group_level" "99";  // must be above this level to be added to oper ldap group
         //"ldap_field_group_member" "memberUid"; // what field group members are in
         //"ldap_timeout" "10"; // seconds
 
@@ -408,8 +411,9 @@
         //   1 = use a registered channel mode, have services op themselves
         //   2 = all of the above, and a channel setting to have ChanServ not
         //       idle in the channel
-        // NOTE: +z mode, needed for this to work,  is inharently flawed and 
-        //       will cause desynch, so don't use it IMO -Rubin.
+        // NOTE: +z mode, needed for this to work. X3 contains modifications to
+       // try and prevent desynchs. If you use this mode do not use any other service
+       // that uses this mode.
         "off_channel" "no";
 
         // Infolines are sent when channel users join the channel. Users set them with USET INFO in X3.
@@ -426,7 +430,7 @@
         // maximum bans on a channel banlist
         "max_chan_bans" "512";
         // maximum length of a user's infoline
-        "max_userinfo_length" "400";  // for god sake lower this. 80 seems good.
+        "max_userinfo_length" "400";  // hard limit for infolines. This is also the default value.
 
         // If SET DynLimit is on and there are N users in the channel, ChanServ will
         // try to keep the limit at N+<adjust_threshold>. This makes the channel