Ignore:
Timestamp:
06/04/07 21:17:16 (5 years ago)
Author:
wd
Message:

The config-files here got nuked somehow (??). Undo the damage, update them
a little, and also update dependencies for the 1459 protocol.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/ithildin/modules/ircd/etc/ircd.conf

    r745 r807  
     1// $Id$ 
     2 
     3/* 
     4** 'global' section: 
     5** this section defines the 'global' settings of the IRC server, each one is 
     6** described as it is laid out. 
     7*/ 
     8 
     9global { 
     10    name "your.server.name.here"; 
     11    network "your-network-here"; 
     12    //address 192.168.42.1; // the ip of the server 
     13    ports 6660-6669,7000,7325; // the port(s) it runs on 
     14    info "your info here"; // the gecos information 
     15    /* 
     16    ** admin sub-section, 
     17    ** each line designates additional administrative information.  Only 
     18    ** one line is required. 
     19    */ 
     20    admin { 
     21        "your"; 
     22        "info"; 
     23        "here"; 
     24    }; 
     25}; 
     26 
     27/* 
     28** protocols section 
     29** this simply defines a list of protocols you will support, you must 
     30** also add modules for these protocols in your module configuration 
     31** file.   Note that the ircd will load rfc1459 for you. 
     32*/ 
     33protocols { 
     34    bahamut14; // the server<->server protocol for bahamut 1.4.34+ servers 
     35}; 
     36 
     37/* 
     38** supported commands to load.  you may want to chuck this section in 
     39** another file,  it can get pretty long.  however, a lot of commands are 
     40** loaded by modules that need them. 
     41*/ 
     42$INCLUDE ircd/commands.conf; 
     43 
     44/* 
     45** addons to load.  stuff like ACLs and other friends (spamguarders and the 
     46** like) are addons 
     47*/ 
     48addon acl; 
     49// acl section included from acl.conf 
     50$INCLUDE ircd/acl.conf; 
     51         
     52addon core; // core support for some channel modes and commands 
     53 
     54/* 
     55** message sets 
     56** these are message groupings which allow you to reformat a lot of the text 
     57** sent to a client.  You can $INCLUDE another file to fill in the data, 
     58** and you need not add a new message for every type!  I recommend creating 
     59** the first (default) set from nothing (thereby using all defaults) 
     60*/ 
     61message-set default {}; 
     62 
     63/* 
     64** privilege sets 
     65** these are sets of privileges granted to users.  they work in a manner very 
     66** similar to the message set system.  Additionally, you can 'include' one 
     67** privilege set in another (settings are overriden from a top-down 
     68** perspective) by simply doing "include <name-of-privilege-set>;'.  It is  
     69** recommended that you create the first (default) set using all the defaults, 
     70** and then create your own per-class definitions.  
     71*/ 
     72privilege-set default {}; 
     73 
     74/* 
     75** class section 
     76** defines connection classes for users, required fields are 
     77** name, ping, max, and sendq (all of them 
     78*/ 
     79 
     80// you should put the default class at the top of the file. 
     81class default { 
     82    ping 180; 
     83    max 600; 
     84    sendq 102400; 
     85}; 
     86 
     87class server { 
     88    ping 300; 
     89    max 0; 
     90    sendq 10485760; // big send queue for servers 
     91}; 
     92 
     93class clients { 
     94    ping 180; // ping timeout frequency 
     95    max 2000; // maximum connections belonging to this class 
     96    sendq 51200; // maximum sendq items for this class. 
     97    flood 60; // set a lowish value, if you see too many innocents flooding 
     98              // off try raising this to 80-100 
     99}; 
     100 
     101class operator { 
     102    ping 300; // give them more time 
     103    max 0; // there is no soft limit on users in this class 
     104    sendq 1048576; // enormous sendqs. 
     105    flood 0; // no flooding off for them. 
     106 
     107    //hostmask "some.host.name"; 
     108    // the 'hostmask' addon allows you to mask users' hostnames if they 
     109    // connect in this class.  it is not loaded by default. 
     110}; 
     111 
     112/* 
     113** operator stuff below 
     114*/ 
     115 
     116privilege-set oper { 
     117    maxchannels 0; // no limit 
     118    see-hidden-channels yes; 
     119    who-see-invisible yes; 
     120    who-reply-limit 0; 
     121    kill global; 
     122    connect remote; 
     123    squit remote; 
     124    operator yes; // this is an operator privilege set 
     125}; 
     126 
     127operator you { 
     128    host "ident@some.host"; // hostnames work 
     129    host "127.0.0.1/8";            // so do CIDR masks 
     130 
     131    pass "md5-password"; 
     132    class "operator"; 
     133    privilege-set oper; 
     134}; 
     135 
     136/* 
     137** server stuff below 
     138*/ 
     139server your.uplink.here { 
     140    address "192.168.42.254"; 
     141    port 4000; 
     142    interval 3m; // try and connect every three minutes 
     143    protocol bahamut14; 
     144    theirpass "their-plaintext-password"; 
     145    ourpass "our-plaintext-password"; 
     146    hub *; // lets them hub anything. 
     147    class server; // be sure to set a server class! 
     148}; 
     149 
Note: See TracChangeset for help on using the changeset viewer.