/****************************************************************************** * GENERAL PARAMETERS CONFIGURATION SECTION. * ******************************************************************************/ /* The general {} block defines general configuration options. */ general { /* (*)helpchan * Network help channel. Shown to users when they request * help for a command that doesn't exist. */ helpchan = "#help"; /* (*)helpurl * Network webpage for services help. Shown to users when they * request help for a command that doesn't exist. */ #helpurl = "http://www.stack.nl/~jilles/irc/atheme-help/"; /* (*)silent * If you want to prevent services from sending * WALLOPS/GLOBOPS about things uncomment this. * Not recommended. */ #silent; /* (*)verbose_wallops * If you want services to send you more information about * events that are occuring (in particular AKILLs), uncomment the * directive below. * * WARNING! This may result in large amounts of wallops/globops * floods. */ #verbose_wallops; /* (*)join_chans * Should ChanServ be allowed to join registered channels? * This option is useful for the fantasy command set. * * If enabled, you can tell ChanServ to join via SET GUARD ON. * * If you use ircu-like ircd (asuka, bircd, undernet), you must * leave this enabled, and put guard in default cflags. * * For ratbox it is recommended to leave it on and put guard in * default cflags, in order that ChanServ does not have to join/part * to do certain things. On the other hand, enabling this increases * potential for bots fighting with ChanServ. * * Regardless of this option, ChanServ will temporarily join * channels which would otherwise be empty if necessary to enforce * akick/restricted/close, and to change the TS if changets is * enabled. */ join_chans; /* (*)leave_chans * Do we leave registered channels after everyone else has left? * Turning this off serves little purpose, except to mark "official" * network channels by keeping them open, and to preserve the * topic and +beI lists. */ leave_chans; /* secure * Do you want to require the use of /msg <service>@<services host>? * Turning this on helps protect against spoofers, but is disabled * as most networks do not presently use it. */ #secure; /* (*)uflags * The default flags to set for usernames upon registration. * Valid values are: hold, neverop, noop, hidemail, nomemo, emailmemos, * enforce, privmsg, private, quietchg and none. */ uflags = { hidemail; }; /* (*)cflags * The default flags to set for channels upon registration. * Valid values are: hold, secure, verbose, verbose_ops, keeptopic, * topiclock, guard, private, nosync, limitflags and none. */ cflags = { verbose; guard; }; /* (*)raw * Do you want to allow SRAs to use the RAW and INJECT commands? * These commands are for debugging. If you don't know how to use them * then don't enable them. They are not supported. */ #raw; /* (*)flood_msgs * Do you want services to detect floods? * Set to how many messages before a flood is triggered. * Note that some messages that need a lot of processing count * as two or four messages. * If services receives `flood_msgs' within `flood_time' the user will * trigger the flood protection. * Setting this to zero disables flood protection. */ flood_msgs = 15; /* (*)flood_time * Do you want services to detect floods? * Set to how long before the counter resets. * If services receives `flood_msgs' within `flood_time' the user will * trigger the flood protection. */ flood_time = 10; /* (*)ratelimit_uses * After how many uses of a command will users be throttled. * After `ratelimit_uses' of a command within `ratelimit_period', users * will not be able to run that ratelimited command until the period is up. * Comment this, ratelimit_period below or both options out to disable rate limiting. * Currently used in helpserv/helpme, helpserv/ticket, hostserv/request, * nickserv/register and chanserv/register. */ ratelimit_uses = 5; /* (*)ratelimit_period * After how much time (in seconds) will the ratelimit_uses counter reset. * After `ratelimit_uses' of a command within `ratelimit_period', users * will not be able to run that ratelimited command until the period is up. * Comment this, ratelimit_uses above or both options out to disable rate limiting. * Currently used in helpserv/helpme, helpserv/ticket, hostserv/request, * nickserv/register and chanserv/register. */ ratelimit_period = 60; /* (*)kline_time * The default expire time for KLINE's in days. * Setting this to 0 makes all KLINE's permanent. */ kline_time = 7; /* (*)clone_time * This is the default expiry time for CLONE exemptions in minutes. * Setting this to 0 makes all CLONE exemptions permanent. */ clone_time = 0; /* commit_interval * The time between database writes in minutes. */ commit_interval = 5; /* (*)default_clone_allowed * The limit after which clones will be KILLed or TKLINEd. * Used by operserv/clones. */ default_clone_allowed = 5; /* (*)default_clone_warn * The limit after which clones will be warned that they may not * have any more concurrent connections. Should be lower than * default_clone_allowed . Used by operserv/clones. */ default_clone_warn = 4; /* (*)clone_identified_increase_limit * If this option is enabled, the clone limit for a IP/host will * be increased by 1 per clone that's identified to services. * This has a limit of double the clone limits above. */ clone_identified_increase_limit; /* (*)uplink_sendq_limit * The maximum amount of data that may be queued to be sent * to the uplink, in bytes. This should be enough to contain * Atheme's response to the netburst, but smaller than the * IRCd's sendq limit for servers. */ uplink_sendq_limit = 1048576; /* (*)language * Language to use for channel and oper messages and as default * for users. */ language = "en"; /* exempts * This block contains a list of user@host masks. Users matching any * of these will not be automatically K:lined by services. */ exempts { }; /* allow_taint * By enabling this option, Atheme will run in configurations where * the upstream will not provide support. By enabling this feature, * you void any perceived rights to support. */ #allow_taint; /* (*)immune_level * This option allows you to customize the operlevel which gets kick * immunity privileges. * * The following flags are available: * immune - require whatever ircd usermode is needed for kick * immunity (this is the default); * admin - require admin privileges for kick immunity * ircop - require any ircop privileges for kick immunity (umode +o) */ immune_level = immune; };