diff options
author | Adam <Adam@anope.org> | 2016-01-03 17:15:31 -0500 |
---|---|---|
committer | Adam <Adam@anope.org> | 2016-01-03 17:16:55 -0500 |
commit | a3c8afae00c54d5b95c620248b51f90679d7d53f (patch) | |
tree | 9ab0bce5cca0e3aa0965bbd58d212144d8c51669 /data | |
parent | 1b24c96ab07d99e5d95ec9337e7b541696b91eb3 (diff) |
Remove various ircservices references in anope.conf
Diffstat (limited to 'data')
-rw-r--r-- | data/anope.example.conf | 104 |
1 files changed, 52 insertions, 52 deletions
diff --git a/data/anope.example.conf b/data/anope.example.conf index a09ce2378..e75b01e74 100644 --- a/data/anope.example.conf +++ b/data/anope.example.conf @@ -1,6 +1,6 @@ /* - * Example configuration file for Services. After making the appropriate - * changes to this file, place it in the Services conf directory (as + * Example configuration file for Anope. After making the appropriate + * changes to this file, place it in the Anope conf directory (as * specified in the "configure" script, default /home/username/anope/conf) * under the name "anope.conf". * @@ -53,7 +53,7 @@ * included to indicate whether an option is required: * * [REQUIRED] - * Indicates a directive which must be given. Without it, Services will + * Indicates a directive which must be given. Without it, Anope will * not start. * * [RECOMMENDED] @@ -71,7 +71,7 @@ * * [DEPRECATED] * Indicates a directive which will disappear in a future version of - * Services, usually because its functionality has been either + * Anope, usually because its functionality has been either * superseded by that of other directives or incorporated into the main * program. */ @@ -120,7 +120,7 @@ define * This section can be included multiple times, and Anope will attempt to * connect to each server until it finally connects. * - * Each uplink IRCd should have a corresponding configuration to allow Services + * Each uplink IRCd should have a corresponding configuration to allow services * to link to it. * * An example configuration for InspIRCd that is compatible with the below uplink @@ -154,20 +154,20 @@ define uplink { /* - * The IP or hostname of the IRC server you wish to connect Services to. - * Usually, you will want to connect Services over 127.0.0.1 (aka localhost). + * The IP or hostname of the IRC server you wish to connect Anope to. + * Usually, you will want to connect over 127.0.0.1 (aka localhost). * * NOTE: On some shell providers, this will not be an option. */ host = "127.0.0.1" /* - * Enable if Services should connect using IPv6. + * Enable if Anope should connect using IPv6. */ ipv6 = no /* - * Enable if Services should connect using SSL. + * Enable if Anope should connect using SSL. * You must have an SSL module loaded for this to work. */ ssl = no @@ -193,12 +193,12 @@ uplink /* * [REQUIRED] Server Information * - * This section contains information about the Services server. + * This section contains information about the services server. */ serverinfo { /* - * The hostname that Services will be seen as, it must have no conflicts with any + * The hostname that services will be seen as, it must have no conflicts with any * other server names on the rest of your IRC network. Note that it does not have * to be an existing hostname, just one that isn't on your network already. */ @@ -208,11 +208,11 @@ serverinfo * The text which should appear as the server's information in /whois and similar * queries. */ - description = "Services for IRC Networks" + description = "Anope IRC Services" /* - * The local address that Services will bind to before connecting to the remote - * server. This may be useful for multihomed hosts. If omitted, Services will let + * The local address that services will bind to before connecting to the remote + * server. This may be useful for multihomed hosts. If omitted, services will let * the Operating System choose the local address. This directive is optional. * * If you don't know what this means or don't need to use it, just leave this @@ -228,7 +228,7 @@ serverinfo #id = "00A" /* - * The filename containing the Services process ID. The path is relative to the + * The filename containing the Anope process ID. The path is relative to the * services root directory. */ pid = "data/anope.pid" @@ -265,32 +265,32 @@ include /* * [REQUIRED] Network Information * - * This section contains information about the IRC network that Services will be + * This section contains information about the IRC network that Anope will be * connecting to. */ networkinfo { /* - * This is the name of the network that Services will be running on. + * This is the name of the network that Anope will be running on. */ networkname = "LocalNet" /* * Set this to the maximum allowed nick length on your network. * Be sure to set this correctly, as setting this wrong can result in - * Services being disconnected from the network. + * services being disconnected from the network. */ nicklen = 31 /* Set this to the maximum allowed ident length on your network. * Be sure to set this correctly, as setting this wrong can result in - * Services being disconnected from the network. + * services being disconnected from the network. */ userlen = 10 /* Set this to the maximum allowed hostname length on your network. * Be sure to set this correctly, as setting this wrong can result in - * Services being disconnected from the network. + * services being disconnected from the network. */ hostlen = 64 @@ -306,7 +306,7 @@ networkinfo /* * Characters allowed in nicknames. This always includes the characters described * in RFC1459, and so does not need to be set for normal behavior. Changing this to - * include characters your IRCd doesn't support will cause your IRCd and/or Services + * include characters your IRCd doesn't support will cause your IRCd and/or services * to break. Multibyte characters are not supported, nor are escape sequences. * * It is recommended you DON'T change this. @@ -318,7 +318,7 @@ networkinfo * to services, such as BotServ bot hostnames and user vhosts. Changing this is not * recommended unless you know for sure your IRCd supports whatever characters you are * wanting to use. Telling services to set a vHost containing characters your IRCd - * disallows could potentially break the IRCd and/or Services. + * disallows could potentially break the IRCd and/or services. * * It is recommended you DON'T change this. */ @@ -343,15 +343,15 @@ networkinfo } /* - * [REQUIRED] Services Options + * [REQUIRED] Anope Options * - * This section contains various options which determine how Services will operate. + * This section contains various options which determine how Anope will operate. */ options { /* * On Linux/UNIX systems Anope can setuid and setgid to this user and group - * after starting up. This is useful if Anope has to bind to privileged ports + * after starting up. This is useful if Anope has to bind to privileged ports. */ #user = "anope" #group = "anope" @@ -370,10 +370,10 @@ options #seed = 9866235 /* - * If set, Services will perform more stringent checks on passwords. If this - * isn't set, Services will only disallow a password if it is the same as the + * If set, services will perform more stringent checks on passwords. If this + * isn't set, services will only disallow a password if it is the same as the * entity (nickname name) with which it is associated. When set, however, - * Services will also check that the password is at least five + * services will also check that the password is at least five * characters long, and in the future will probably check other things * as well. * @@ -382,11 +382,11 @@ options strictpasswords = yes /* - * Sets the number of invalid password tries before Services removes a user + * Sets the number of invalid password tries before services removes a user * from the network. If a user enters a number of invalid passwords equal to - * the given amount for any Services function or combination of functions - * during a single IRC session (subject to badpasstimeout, below), Services - * will issues a /KILL for the user. If not given, Services will ignore + * the given amount for any services function or combination of functions + * during a single IRC session (subject to badpasstimeout, below), services + * will issues a /KILL for the user. If not given, services will ignore * failed password attempts (though they will be logged in any case). * * This directive is optional, but recommended. @@ -428,7 +428,7 @@ options /* * Sets the (maximum) frequency at which the timeout list is checked. This, * combined with readtimeout above, determines how accurately timed events, - * such as nick kills, occur; it also determines how much CPU time Services + * such as nick kills, occur; it also determines how much CPU time services * will use doing this. Higher values will cause less accurate timing but * less CPU usage. * @@ -441,7 +441,7 @@ options timeoutcheck = 3s /* - * If set, this will allow users to let Services send PRIVMSGs to them + * If set, this will allow users to let services send PRIVMSGs to them * instead of NOTICEs. Also see the "msg" option of nickserv:defaults, * which also toggles the default communication (PRIVMSG or NOTICE) to * use for unregistered users. @@ -454,7 +454,7 @@ options #useprivmsg = yes /* - * If set, will force Services to only respond to PRIVMSGs addresses to + * If set, will force services to only respond to PRIVMSGs addresses to * Nick@ServerName - e.g. NickServ@localhost.net. This should be used in * conjunction with IRCd aliases. This directive is optional. * @@ -463,14 +463,14 @@ options #usestrictprivmsg = yes /* - * If set, Services will only show /stats o to IRC Operators. This directive + * If set, services will only show /stats o to IRC Operators. This directive * is optional. */ #hidestatso = yes /* * A space-separated list of ulined servers on your network, it is assumed that - * the servers in this list are allowed to set channel modes and Services will + * the servers in this list are allowed to set channel modes and services will * not attempt to reverse their mode changes. * * WARNING: Do NOT put your normal IRC user servers in this directive. @@ -485,13 +485,13 @@ options retrywait = 60s /* - * If set, Services will hide commands that users don't have the privilege to execute + * If set, services will hide commands that users don't have the privilege to execute * from HELP output. */ hideprivilegedcommands = yes /* - * If set, Services will hide commands that users can't execute because they are not + * If set, services will hide commands that users can't execute because they are not * logged in from HELP output. */ hideregisteredcommands = yes @@ -523,7 +523,7 @@ options * [REQUIRED] Casemapping configuration * * Includes the configuration for the casemap services should use. - * Services use this case map to compare, with case insensitivity, + * Anope uses this case map to compare, with case insensitivity, * things such as nick names, channel names, etc. * * Two casemaps shipped with Anope are ascii and rfc1459. @@ -764,7 +764,7 @@ log * nickserv/drop - Can drop other users nicks * operserv/config - Can modify services's configuration * operserv/oper/modify - Can add and remove operators with at most the same privileges - * protected - Can not be kicked from channels by Services + * protected - Can not be kicked from channels by services * * Available commands: * botserv/bot/del botserv/bot/add botserv/bot/change botserv/set/private @@ -869,10 +869,10 @@ opertype * After defining different types of operators in the above opertype section, we now define who is in these groups * through 'oper' blocks, similar to ircd access. * - * The default is to comment these out (so NOBODY will have Services access). + * The default is to comment these out (so NOBODY will have access). * You probably want to add yourself and a few other people at minimum. * - * As with all permissions, make sure to only give trustworthy people access to Services. + * As with all permissions, make sure to only give trustworthy people access. */ #oper @@ -883,7 +883,7 @@ opertype /* The opertype this person will have */ type = "Services Root" - /* If set, the user must be an oper on the IRCd to gain their Services + /* If set, the user must be an oper on the IRCd to gain their * oper privileges. */ require_oper = yes @@ -918,7 +918,7 @@ opertype /* * [OPTIONAL] Mail Config * - * This section contains settings related to the use of e-mail from Services. + * This section contains settings related to the use of e-mail from services. * If the usemail directive is set to yes, unless specified otherwise, all other * directives are required. * @@ -929,7 +929,7 @@ opertype mail { /* - * If set, this option enables the mail commands in Services. You may choose + * If set, this option enables the mail commands in Anope. You may choose * to disable it if you have no Sendmail-compatible mailer installed. Whilst * this directive (and entire block) is optional, it is required if * nickserv:registration is set to yes. @@ -960,7 +960,7 @@ mail * another e-mail after they have sent one. It also controls the minimum time * a user must wait before they can receive another e-mail. * - * This feature prevents users from being mail bombed using Services and + * This feature prevents users from being mail bombed using services and * it is highly recommended that it be used. * * This directive is optional, but highly recommended. @@ -968,7 +968,7 @@ mail delay = 5m /* - * If set, Services will not attempt to put quotes around the TO: fields + * If set, Anope will not put quotes around the TO: fields * in e-mails. * * This directive is optional, and as far as we know, it's only needed @@ -1073,18 +1073,18 @@ module /* * Sets the number of days backups of databases are kept. If you don't give it, - * or if you set it to 0, Services won't backup the databases. + * or if you set it to 0, Anope won't backup the databases. * - * NOTE: Services must run 24 hours a day for this feature to work. + * NOTE: Anope must run 24 hours a day for this feature to work. * * This directive is optional, but recommended. */ keepbackups = 3 /* - * Allows Services to continue file write operations (i.e. database saving) + * Allows Anope to continue file write operations (i.e. database saving) * even if the original file cannot be backed up. Enabling this option may - * allow Services to continue operation under conditions where it might + * allow Anope to continue operation under conditions where it might * otherwise fail, such as a nearly-full disk. * * NOTE: Enabling this option can cause irrecoverable data loss under some |