Ircd (services.conf)

Configuração de serviços como chanserv para sua rede de irc, botserv, etc.

Categoria: Networking

Software: Ircd

[ Hits: 14.832 ]

Por: Grégory H. Ebertz


Chanserv, Botserv, Nickserv e tudo mais para controle de sua rede de Ircd.  Basta reconfigurar e colocar para funcionar no epona 1.4.0.


#Feito Por Grégory H. Ebertz
# changes to this file, place it in the Services data directory (as
# specified in the "configure" script, default /usr/local/lib/services)
# under the name "services.conf".
#
# The format of this file is fairly simple: a line beginning with a # is a
# comment, and any other non-blank line is expected to be a directive and
# parameters, separated by spaces or tabs.  For example:
#
#   Directive Parameter-1 Parameter-2 ...
#
# Directives are case-insensitive.  Note that some directives do not take
# any parameters; these are typically "on-off" directives, for which simply
# including the directive in this file (or removing it) has an effect on
# Services' functionality.
#
# If a parameter's value is a string which includes spaces, enclose the
# string in double quotation marks, like the example below.  Quotes may be
# used around any string at all for clarity.
#
#   "This is a parameter string with spaces in it"
#
# If you need to include a double quote inside a quoted string, precede it
# by a backslash:
#
#   "This string has \"double quotes\" in it"
#
# Time parameters can be specified either as an integer representing a
# number of seconds (e.g. "3600" = 1 hour), or as an integer with a unit
# specifier: "s" = seconds, "m" = minutes, "h" = hours, "d" = days.
# Combinations (such as "1h30m") are not permitted.  Examples (all of which
# represent the same length of time, one day):
#
#   "86400", "86400s", "1440m", "24h", "1d"
#
# In the documentation for each directive, one of the following will be
# included to indicate whether an option is required:
#
# [REQUIRED]
#     Indicates a directive which must be given.  Without it, Services will
#     not start.
#
# [RECOMMENDED]
#     Indicates a directive which may be omitted, but omitting it may cause
#     undesirable side effects.
#
# [OPTIONAL]
#     Indicates a directive which is optional.  If not given, the feature
#     will typically be disabled.  If this is not the case, more
#     information will be given in the documentation.
#
# [DISCOURAGED]
#     Indicates a directive which may cause undesirable side effects if
#     specified.
#
# [DEPRECATED]
#     Indicates a directive which will disappear in a future version of
#     Services, usually because its functionality has been either
#     superseded by that of other directives or incorporated into the main
#     program.

##########################
#
# Remote server configuration
#
##########################

# RemoteServer <hostname> <port> <password>  [REQUIRED]
#     Specifies the remote server hostname and port.  The hostname may
#     either be a standard Internet hostname or dotted-quad numeric
#     address; the port number must be an integer between 1 and 65535
#     inclusive.  The password is a string which should be enclosed in
#     double quotes if it contains any spaces (or just for clarity).
#
#     The remote server and port may be overridden at runtime with the
#     -remote command-line option.  The password may not be set at runtime.

RemoteServer    localhost.com.br  6667 "senha"

# LocalAddress <hostname> [port]  [OPTIONAL]
#     Specifies the local address to bind to before connecting to the
#     remote server.  This may be useful on multihomed hosts.  The hostname
#     and port number are specified the same way as with the RemoteServer
#     directive.  If this is not specified, Services will let the operating
#     system choose the local address.  If only a hostname is specified,
#     Services will bind to that address but let the operating system
#     choose the local port number.
#
#     If you don't know what this means or don't need to use it, just leave
#     the directive commented out.
#
#     This directive may be overridden at runtime by the -local
#     command-line option.

#LocalAddress   nowhere. 0

#######################################
#
# Services identification and pseudoclient names
#
#######################################

# ServerName <name>  [REQUIRED]
#     Specifies the IRC server name which Services should use.  May be
#     overridden by the -name command-line option.

ServerName  "services.data6.datacenter.psi.br"

# ServerDesc <text>  [REQUIRED]
#     Specifies the text which should appear as the server's information in
#     /whois and similar queries.  May be overridden by the -desc
#     command-line option.

ServerDesc  "Services for IRC Networks"

# ServiceUser <usermask>  [REQUIRED]
#     Specifies the [email protected] mask which should be used by the Services
#     pseudoclients.  May be overridden by the -user and -host command-line
#     options.

ServiceUser "[email protected]"

# ...Name <nick> <string>  [REQUIRED except as noted below]
#     Specify the nicknames (first parameter) and "real" names (second
#     parameter) for the Services pseudoclients.  BotServ and DevNull may
#     be disabled by commenting out the appropriate lines below. Disabling
#     BotServ is recommended on large networks.

NickServName    "NickServ"  "Nickname Server"
ChanServName    "ChanServ"  "Channel Server"
MemoServName    "MemoServ"  "Memo Server"
BotServName     "BotServ"   "Bot Server"
HelpServName    "HelpServ"  "Help Server"
OperServName    "OperServ"  "Operator Server"
GlobalName      "Global"    "Global Noticer"
#DevNullName     "DevNull"   "/dev/null -- message sink"

############################
#
# Services data filenames
#
############################

# NOTE: All filenames are relative to the Services data directory.

# PIDFile <filename>  [REQUIRED]
#     Specifies the name of the file containing Services' process ID.

PIDFile     services.pid

# MOTDFile <filename>  [REQUIRED]
#     Specifies the name of the Message of the Day file.

MOTDFile    services.motd

# ...DB <filename>  [REQUIRED]
#     Specifies the filenames for the various Services subsystems' databases.

NickServDB  nick.db
ChanServDB  chan.db
BotServDB   bot.db
OperServDB  oper.db
NewsDB      news.db
ExceptionDB exception.db

# There is no more databases for AKILLs. This setting is kept to allow
# you to import old AKILL database, and is optional. (If not given,
# Services will look for a file named akill.db.)

# AutokillDB    akill.db

#############################
#
# Network information
#
#############################

# HelpChannel <channel> [OPTIONAL]
#
#     When defined, every users that got op on this channel automatically 
#     receive the +h user mode.

HelpChannel "#ajuda"

# NetworkDomain <name> [OPTIONAL]
#
#     If your network has a common domain name, specify it there (for
#     example, all Langochat servers have a name ending in ".langochat.net",
#     so "langochat.net" would be set there. It will be used by the OperServ 
#     GLOBAL command, and if you don't have a common domain name, this 
#     command may just not work.

NetworkDomain "datacenter.psi.br"

# NetworkName <name> [REQUIRED]
# 
#     This is the name of the network the Services are running on.

NetworkName "Data Center Internet"

###########################
#
# Basic functionality
#
###########################

# NoBackupOkay  [DISCOURAGED]
#     Allows Services 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 some conditions
#     when it might otherwise fail, such as a nearly-full disk.
#
#     *** NOTE ***
#     Enabling this option can cause irrecoverable data loss under some
#     conditions, so make CERTAIN you know what you're doing when you
#     enable it!

#NoBackupOkay

# ListOpersOnly  [DEPRECATED]
#     When enabled, limits use of the ChanServ and NickServ LIST commands
#     to IRC operators.
#
#     This directive has been superseded by the NSListOpersOnly and
#     CSListOpersOnly directives.

#ListOpersOnly

# StrictPasswords  [RECOMMENDED]
#     When enabled, causes Services to perform more stringent checks on
#     passwords.  If this is disabled, Services will only disallow a
#     password if it is the same as the entity (nickname or channel name)
#     with which it is associated.  When enabled, however, Services will
#     also check that the password is at least five characters long, and
#     in the future will probably check other things as well.

StrictPasswords

# BadPassLimit <count>  [RECOMMENDED]
#     Sets the number of invalid password tries before Services removes a
#     user from the network.  If a user enters <count> invalid passwords
#     for any Services function or combination of functions during a
#     single IRC session (subect to BadPassTimeout, below), Services will
#     issue a /KILL for the user.  If not given, Services will ignore
#     failed password attempts (though they will be logged in any case).

BadPassLimit    6

# BadPassTimeout <time>  [OPTIONAL]
#     Sets the time after which invalid passwords are forgotten about.  If
#     a user does not enter any incorrect passwords in this amount of time,
#     the incorrect password count will reset to zero.  If not given, the
#     timeout will be disabled, and the incorrect password count will never
#     be reset until the user disconnects.

BadPassTimeout  1h

# UpdateTimeout <time>  [REQUIRED]
#     Sets the delay between automatic database updates.  This timer is
#     reset by the OperServ UPDATE command.

UpdateTimeout   5m

# ExpireTimeout <time>  [REQUIRED]
#     Sets the delay between checks for expired nicknames and channels.
#     The OperServ UPDATE command will also cause a check for expiration
#     and reset this timer.

ExpireTimeout   30m

# ReadTimeout <time>  [REQUIRED]
#     Sets the timeout period for reading from the network.

ReadTimeout 5s

# WarningTimeout <time>  [REQUIRED]
#     Sets the interval between sending warning messages for program
#     errors via WALLOPS/GLOBOPS.

WarningTimeout  4h

# TimeoutCheck <time>  [REQUIRED]
#     Sets the (maximum) frequency at which the timeout list is checked.
#     This, combined with ReadTimeout above, determine how accurately timed
#     events, 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.
#
#     This shouldn't be set any higher than 10 seconds, and 1 second is
#     best if your system is powerful enough (or your network small enough)
#     to handle it.  0 will cause the timeout list to be checked every time
#     through the main loop, which will probably slow down Services too
#     much to be useful on most networks.
#
#     Note that this value is not an absolute limit on the period between
#     checks of the timeout list; the period may be as great as ReadTimeout
#     (above) during periods of inactivity.

TimeoutCheck    3s

# KeepLogs <days> [RECOMMENDED]
#
#     Sets the number of days log files are kept. If you don't give it, or if
#     you set it to 0, logs will be kept undefinitely.
#
#     NOTE: Services must run 24 hours a day for this feature to work.

KeepLogs 7

# KeepBackups <days> [RECOMMENDED]
#
#     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.
#
#     NOTE: Services must run 24 hours a day for this feature to work.

KeepBackups 3

# ForceForbidReason [OPTIONAL]
#
#     If set, Services will require a reason when a forbid is added, else
#     the reason is optional.

ForceForbidReason

# UsePrivmsg [OPTIONAL]
#
#    This directive will make Services send PRIVMSGs to users instead of
#    NOTICEs by default, and allow users to set how Services should 
#    communicate with them. 
#
#    This is a feature that is against the IRC RFC and should be used 
#    _only_ if absolutely necessary.


#UsePrivmsg

# DumpCore [OPTIONAL]
#
#    Setting this directive will make Epona dump core when a segmentation
#    fault occurs. This is generally not needed, but if Epona is crashing
#    on your network and you want to make a bug report, having a core
#    file may be of great help.

#DumpCore

# LogUsers [OPTIONAL]
#
#    Defines whether Epona will log user connections, disconnections and
#    nickname changes. You may have to do so in case you ever need to
#    transmit user information to your local authorities.

#LogUsers

###########################
#
# Mail-related options
#
###########################

# NOTE: if UseMail is not set, all parameters after it in this section
# are optional.

# UseMail [OPTIONAL]
#
# This option enables the mail commands in Services. You may choose
# to disable it if you haven't a sendmail-compatible mailer installed.

UseMail

# SendMailPath <path> [REQUIRED]
#
# This is how we should call SendMail to send a mail. It must be
# called with all parameters needed to make it scan the mail input
# to find the mail recipient; consult your SendMail documentation.
#
# Postfix users must use the compatible sendmail utility provided
# with it; this one needs no parameters on the command line.

SendMailPath "/usr/sbin/sendmail -t"

# SendFrom <e-mail> [REQUIRED]
#
# This is the e-mail from which all the e-mails are to be sent. It should
# really exist.

SendFrom [email protected]

# RestrictMail [OPTIONAL]
#
# When enabled, SENDPASS will be restricted to IRC operators.
#
# WARNING: if you choose to not enable this option, you should limit
# the number of processes the services user can have at a time (you can
# create a special user for this; remember to never launch Services as root).

RestrictMail

# MailDelay <time> [RECOMMENDED]
#
# This controls the minimum amount of time an user must wait before sending
# another mail after it has sent one. It also controls the minimum time
# an user must wait before it can receive another mail.
#
# This feature prevents users from being mail bombed using Services and
# should definitely be used.

MailDelay 5m

#######################
#
# Proxy detection
#
#######################

# Note: if ProxyDetect is not set, all parameters after it in this section
# are optional.

# ProxyDetect [OPTIONAL]
#    
# Enables insecure proxy detection. Services will automatically
# scan each incoming user and akill those that use insecure proxy.
#
# Epona currently supports detection of Wingate (port 23), SOCKS4/5 
# (port 1080), and HTTP proxy (ports 3128 and 8080). It uses the
# protocol of each proxy type to connect to an IRC server, it does
# not only check if the port is open (so your users may still have
# an open telnet server on their port 23 for example).
#
# WARNING: You should get the authorization of the administrator of
# the computer which runs the proxy detector before enabling it; not
# all administrators will accept it. Also note that in certain 
# countries, port scanning is prohibited. 
#
# This feature requires threading support to be compiled into Epona.

ProxyDetect

# ProxyThreads <number> [REQUIRED]
#
# Sets the number of threads Services will launch when starting. Each
# thread will have the responsability to scan queued hostname for 
# proxies.
#
# This value must be set depending of the number of users you have
# on your network. The more threads are used, the more simultaneous
# checks can be done. Remember however, that threads are 
# resource-consuming. 
# 
# WARNING: On Linux, each thread takes a background process, and there
# is an additional process used for thread management; this is a problem
# if you are limited in the number of background process you can use 
# (on a paid shell for example).

ProxyThreads 5

# ProxyMessage... <message> [RECOMMENDED]
#
# Sets the notices that will be sent out to users before Services
# scan them for proxy. You may not use all of them, but just as much as 
# necessary.

ProxyMessage1 "I will now detect if you're using an insecure proxy."
ProxyMessage2 "If you see a connection on port 23, 1080, 3128 or 8080 from"
ProxyMessage3 "my.box.net, please disregard it, as it is the detector in action."
ProxyMessage4 "See http://proxy.myirc.net/ for information about our proxy policy."
#ProxyMessage5 "Enter"
#ProxyMessage6 "whatever"
#ProxyMessage7 "you want"
#ProxyMessage8 "here."

# ProxyCheck... [OPTIONAL]
#
# Determines what types of proxy Epona will try to find (respectively 
# Wingate on port 23, SOCKS4 on port 1080, SOCKS5 on port 1080, HTTP 
# proxy on port 3128, HTTP proxy on port 8080 and HTTP proxy on port
# 80).

ProxyCheckWingate
ProxyCheckSocks4
ProxyCheckSocks5
ProxyCheckHTTP1
ProxyCheckHTTP2
ProxyCheckHTTP3

# ProxyTimeout <time> [REQUIRED]

# Sets the maximum length of time we allow a connect/read operation to 
# take. If you set this value too high, your threads may hang on a single
# check for a very long time. The best is to try different values
# and see which one is the more efficient for your network.

ProxyTimeout 15s

# ProxyTestServer <ip> <port> [REQUIRED]
#
# Sets the *IP* and port of the IRC server to use as a target when 
# testing users for proxy.

ProxyTestServer "1.2.3.4" 6667

# ProxyExpire <time> [RECOMMENDED]
#
# Sets the length of time before a proxy host cache entry expires, if
# not used.

ProxyExpire 30d

# ProxyCacheExpire <time> [REQUIRED]
#
# Sets the length of time before a normal host cache entry expires, if
# not used. This cannot be set to 0d.
#
# Every non-proxy hosts will be stored in cache (to avoid too many scans
# to the same host), so you should set this enough low to not fill your
# memory, especially on large networks.

ProxyCacheExpire 1d

# ProxyAkillReason <reason>
#
# Sets the reason that will be used to AKILL an user from the network
# if a proxy is detected.

ProxyAkillReason "You're using an insecure proxy. See http://proxy.myirc.net/config.html for information about how to config your proxy in a safe manner."

# WallProxy [OPTIONAL]
#
# Sends a WALLOPS/GLOBOPS when an user using an insecure proxy is being
# AKILLed.

WallProxy

# ProxyMax <number> [REQUIRED]
#
# Sets the maximum proxy cache entries that can be displayed in a single
# call to OperServ CACHE.

ProxyMax 50

#########################
#
# NickServ configuration
#
#########################

# NSForceEmail [RECOMMENDED]
#     This option forces the users to give an e-mail when they register
#     a nickname. If you have nicks in the database that have no e-mail
#     set, they will be asked to set an e-mail when they identify their
#     nickname until they set one. Also, this option prevents user from
#     unsetting the password.
#
#     This option is useful to resolve "lost password" problems.

NSForceEmail

# NSDef...  [OPTIONAL]
#     Sets the default options for newly registered nicks.  Note that
#     changing these options will have no effect on nicks which are already
#     registered.
#
#     If both NSDefKill and NSDefKillQuick are given, the latter takes
#     precedence.  KILL IMMED cannot be specified as a default.
#
#     NOTE:  If you do not enable any of these options, a default of
#     Secure, MemoSignon, and MemoReceive will be used, for backward
#     compatibility.  If you really want no options enabled by default, use
#     NSDefNone.

#NSDefNone

#NSDefKill
#NSDefKillQuick
NSDefSecure
#NSDefPrivate
NSDefHideEmail
#NSDefHideUsermask
#NSDefHideQuit
#NSDefMsg
NSDefMemoSignon
NSDefMemoReceive

# NSDefLanguage <language-number> [REQUIRED]
#     Sets the default language non and newly-registered will receive
#     services' messages in. The numbers are the same than those
#     used for the /nickserv SET LANGUAGE command, so look the help
#     of this command for the list of currently supported languages.
#     
#     If you ever wanted to know how to translate services in your 
#     language, read the chapter about it in the README.

NSDefLanguage 1

# NSRegDelay <time>  [RECOMMENDED]
#     Sets the minimum length of time between consecutive uses of the
#     REGISTER command.  If not given, this restriction is disabled (note
#     that this allows "registration flooding").

NSRegDelay  30s

# NSExpire <time>  [RECOMMENDED]
#     Sets the length of time before a nick registration expires.

NSExpire    21d

# NSMaxAliases <number> [RECOMMENDED]
#     Sets the maximum number of nicks allowed in a group. If you
#     set it to 0, or don't set it at all, no limits will be applied.

NSMaxAliases    16

# NSAccessMax <count>  [REQUIRED]
#     Sets the maximum number of entries allowed on a nickname access list.

NSAccessMax 32

# NSEnforcerUser <user>[@<host>]  [REQUIRED]
#     Sets the username (and possibly hostname) used for the fake user
#     created when NickServ collides a user.  Should be in [email protected]
#     format.  If the host is not given, the one from ServicesUser is
#     used.

NSEnforcerUser  [email protected]
#NSEnforcerUser enforcer

# NSReleaseTimeout <time>  [REQUIRED]
#     Sets the delay before a NickServ-collided nick is released.

NSReleaseTimeout 1m

# NSAllowKillImmed  [OPTIONAL]
#     When enabled, allows the use of the IMMED option with the NickServ
#     SET KILL command.

#NSAllowKillImmed

# NSNoGroupChange [OPTIONAL]
#   When enabled, the NickServ GROUP command won't allow any group change.
#   This is recommended for better performances and to protect against
#   nick stealing, however users will have less flexibility.

#NSNoGroupChange

# NSListOpersOnly  [OPTIONAL]
#     When enabled, limits use of the NickServ LIST command to IRC
#     operators.

#NSListOpersOnly

# NSListMax <count>  [REQUIRED]
#     Specifies the maximum number of nicks to be returned for a NickServ
#     LIST command.

NSListMax   50

# NSGuestNickPrefix <value>  [REQUIRED]
#     When a user's nick is forcibly changed to enforce a "nick kill", their
#     new nick will start with this value. The rest will be made up of 6 or 7
#     digits.

NSGuestNickPrefix   "DataCenter"

# NSSecureAdmins  [RECOMMENDED]
#     When enabled, prevents the use of the DROP, FORBID, GETPASS, and 
#     SET PASSWORD commands by Services admins on other Services admins or 
#     the Services root.

NSSecureAdmins

# NSStrictPrivileges [RECOMMENDED]
#   
# When enabled, any user wanting to use the privileges of Services Root, Services 
# Admin or Services Operator must have been logged as an IRC Operator with the
# /oper command.

NSStrictPrivileges

###########################
#
# ChanServ configuration
#
###########################

# CSDef...  [OPTIONAL]
#     Sets the default options for newly registered channels.  Note that
#     changing these options will have no effect on channels which are 
#     already registered.
#
#     NOTE:  If you do not enable any of these options, a default of
#     KeepTopic, Secure, SecureFounder and SignKick will be used, for 
#     backward compatibility.  If you really want no options enabled by 
#     default, use CSDefNone.

#CSDefNone

CSDefKeepTopic
#CSDefOpNotice
CSDefPeace
#CSDefPrivate
#CSDefRestricted
CSDefSecure
#CSDefSecureOps
CSDefSecureFounder
CSDefSignKick
#CSDefSignKickLevel
#CSDefTopicLock
CSDefXOP


# CSMaxReg <count>  [RECOMMENDED]
#     Limits the number of channels which may be registered to a single
#     nickname.

CSMaxReg    20

# CSExpire <time>  [RECOMMENDED]
#     Sets the number of days before a channel expires.

CSExpire    14d

# CSDefBantype <bantype> [REQUIRED]
#
# Sets the default ban type for newly registered channels (and when
# importing old databases).
#
# bantype can be:
# 
# 0: ban in the form *[email protected]
# 1: ban in the form *!*[email protected]
# 2: ban in the form *!*@host
# 3: ban in the form *!*[email protected]*.domain

CSDefBantype 2

# CSAccessMax <count>  [REQUIRED]
#     Sets the maximum number of entries on a channel's access list.
#     Channel access lists may contain only registered nicknames;
#     therefore, checking each entry on the list requires only a single
#     scaler comparison instead of a wildcard match, and this limit may be
#     safely set much higher than (for exmple) the nickname access list
#     size limit without impacting performance significantly.

CSAccessMax 1024

# CSAutokickMax <count>  [REQUIRED]
#     Sets the maximum number of entries on a channel's autokick list.

CSAutokickMax   32

# CSAutokickReason <text>  [REQUIRED]
#     Sets the default reason for an autokick if none is given.

CSAutokickReason "User has been banned from the channel"

# CSInhabit <time>  [REQUIRED]
#     Sets the length of time ChanServ stays in a channel after kicking a
#     user from a channel s/he is not permitted to be in.  This only occurs
#     when the user is the only one in the channel.

CSInhabit   15s

# CSListOpersOnly  [OPTIONAL]
#     When enabled, limits use of the ChanServ LIST command to IRC
#     operators.

#CSListOpersOnly

# CSListMax <count>  [REQUIRED]
#     Specifies the maximum number of channels to be returned for a
#     ChanServ LIST command.

CSListMax   50

#############################
#
# MemoServ configuration
#
#############################

# MSMaxMemos <count>  [RECOMMENDED]
#     Sets the maximum number of memos a user is allowed to keep by
#     default.  Normal users may set the limit anywhere between zero and
#     this value; Services admins can change it to any value or disable it.
#     If not given, the limit is disabled by default, and normal users can
#     set any limit they want.

MSMaxMemos  20

# MSSendDelay <time>  [RECOMMENDED]
#     Sets the delay between consecutive uses of the MemoServ SEND command.
#     This can help prevent spam as well as denial-of-service attacks from
#     sending large numbers of memos and filling up disk space (and
#     memory).  A 3-second wait means a maximum average of 150 bytes of
#     memo per second per user under the current IRC protocol.

MSSendDelay 3s

# MSNotifyAll  [OPTIONAL]
#     Should we notify all appropriate users of a new memo?  This applies
#     in cases where a memo is sent to a nick which is in the group of
#     another nick. Note that, unlike before, it is currently often more
#     efficient to enable this.

MSNotifyAll

##############################
#
# BotServ configuration
#
##############################

# BSDef...  [OPTIONAL]
#     Sets the default options for newly registered channels.  Note that
#     changing these options will have no effect on channels which are 
#     already registered.

#BSDefDontKickOps
#BSDefDontKickVoices
#BSDefGreet
#BSDefFantasy
#BSDefSymbiosis

# BSMinUsers <count> [REQUIRED]
#    Minimum number of users there must be in a channel before the
#    bot joins it. The best value for this setting is 1 or 2. This
#    cannot be 0, otherwise topic retention and mode lock and such
#    other things won't work.

BSMinUsers 1

# BSBadWordsMax <count> [REQUIRED]
#    Maximum number of entries a single bad words list can have.
#    Setting it too high can reduce performances slightely.

BSBadWordsMax 32

# BSKeepData <time> [REQUIRED]
#    Number of time data for an user that is used by BotServ kickers are 
#    valid. If the data exceeds this time, it is reset or deleted
#    depending the case. Do not set it too high otherwise your resources
#    will be slightely affected.

BSKeepData 10m

# BSSmartJoin [OPTIONAL]
#    The bot is currently not affected by any modes or bans when he
#    tries to join a channel. But some people may want to make it
#    act like a real bot, that is, for example, remove all bans
#    that affect the bot before joining the channel, remove a 
#    ban that affects the bot set by an user when it is on the
#    channel, and so on. Since it consumes a bit more CPU time,
#    you should not comment it out on larger networks.

# BSSmartJoin

# BSGentleBWReason [OPTIONAL]
#    This option will make the bot use a kick reason that does not retake
#    the word when it is kicking the bot. This is especially useful if
#    you have young people on your network.

BSGentleBWReason

#############################
#
# OperServ configuration
#
#############################

# ServicesRoot <nicks>  [REQUIRED]
#    Specifies the Services "super-users".  The super-users, or "roots" as in
#    Unix terminology, are the only users who can add or delete Services
#    admins.
#
#    You can specify more than one nick by separating each one by a space.
#
#    This is commented out by default; make sure you insert the correct
#    nick before uncommenting it.

ServicesRoot   "Lan_Gregy_Cdia"

# LogMaxUsers  [OPTIONAL]
#    Causes Services to write a message to the log every time a new user
#    maximum is set.

LogMaxUsers

# ...Expiry <time>  [REQUIRED]
#     Sets the default expiry time for, respectively, AKILLs, SGLINEs,
#     SQLINEs and SZLINEs.

AutoKillExpiry  30d
SGLineExpiry    30d
SQLineExpiry    30d
SZLineExpiry    30d

# AkillOnAdd [OPTIONAL]
#
# When enabled, this option makes the services send an AKILL command
# immediately after it has been added with AKILL ADD. This eliminates
# the need of killing the users after the akill has been added.

# AkillOnAdd

# KillClonesAkillExpire <time>  [REQUIRED]
#     Sets the expiry time for autokills added for hosts that have been
#     killed using the KILLCLONES command.

KillClonesAkillExpire   30m

# DisableRaw [RECOMMENDED]
#
# Disables the highly destructive OperServ RAW command.

DisableRaw

# WallOper  [OPTIONAL]
#     Causes Services to send a WALLOPS/GLOBOPS when a user becomes an IRC
#     operator.  Note that this can cause WALLOPS floods when Services
#     first connects to the network.

#WallOper

# WallBadOS  [OPTIONAL]
#     Causes Services to send a WALLOPS/GLOBOPS if a non-IRC-operator tries
#     to use OperServ.

#WallBadOS

# WallOS...  [OPTIONAL]
#     Cause Services to send a WALLOPS/GLOBOPS on use of each of the
#     OperServ commands listed.

#WallOSGlobal
#WallOSMode
#WallOSClearmodes
#WallOSKick
#WallOSAkill
#WallOSSGLine
#WallOSSQLine
#WallOSSZLine
#WallOSNoOp
#WallOSJupe
#WallOSRaw

# Wall...Expire  [OPTIONAL]
#     Causes Services to send a WALLOPS/GLOBOPS whenever respectively 
#     an AKILL, an SGLINE, an SQLINE, an SZLINE and a session limit 
#     exception expires.

#WallAkillExpire
#WallSGLineExpire
#WallSQLineExpire
#WallSZLineExpire
#WallExceptionExpire

# WallGetpass  [OPTIONAL]
#     Causes Services to send a WALLOPS/GLOBOPS on use of the NickServ or
#     ChanServ GETPASS command.

WallGetpass

# WallSetpass  [OPTIONAL]
#     Causes Services to send a WALLOPS/GLOBOPS whenever a Services admin
#     sets a password for a nickname or channel s/he does not normally have
#     privileges to set.

WallSetpass

# WallForbid [OPTIONAL]
#     Causes Services to send a WALLOPS/GLOBOPS on use of the NickServ or
#     ChanServ FORBID command.

WallForbid

# WallDrop [OPTIONAL]   
#     Causes Services to send a WALLOPS/GLOBOPS whenever a Services admin
#     drops a nickname or channel s/he does not normally have
#     privileges to drop.

WallDrop

# LimitSessions  [OPTIONAL]
#     Enables session limiting. Session limiting prevents users from 
#     connecting more than a certain number of times from the same host at the
#     same time - thus preventing most types of cloning. Once a host reaches 
#     it's session limit, all clients attempting to connect from that host 
#     will be killed. Exceptions to the default session limit, which are based 
#     on host names, can be defined via the exception list. It should be noted
#     that session limiting, along with a large exception list, can degrade
#     services' performance. See the source and comments in sessions.c and the
#     online help for more information about session limiting.
#
#     Session limiting is meant to replace the CheckClones and KillClones
#     code. It is therefore highly recommened that they are disabled when
#     session limiting has been enabled.
#
#     NOTE:  This option is not available when STREAMLINED is defined in
#     the Makefile.

LimitSessions

# DefSessionLimit <limit>  [REQUIRED]
#     Default session limit per host. Once a host reaches it's session limit,
#     all clients attempting to connect from that host will be killed. A value
#     of zero means an unlimited session limit.

DefSessionLimit 3

# MaxSessionLimit <limit>  [REQUIRED]
#     The maximum session limit that may be set for a host in an exception.

MaxSessionLimit 100

# ExceptionExpiry <time>  [REQUIRED]
#     Sets the default expiry time for exceptions.

ExceptionExpiry 1d

# SessionLimitExceeded <message>  [OPTIONAL]
#     The message that will be NOTICE'd to a user just before they are removed
#     from the network because their's host session-limit has been exceeded. 
#     It may be used to give a slightly more descriptive reason for the
#     impending kill as apposed to simply "Session limit exceeded". If this is
#     commented out, nothing will be sent.

SessionLimitExceeded "The session limit for your host %s has been exceeded."

# SessionLimitDetailsLoc <message>  [OPTIONAL]
#     Same as above, but should be used to provide a website address where
#     users can find out more about session limits and how to go about 
#     applying for an exception. If this is commented out, nothing will be
#     sent.
#
#     This option has been intentionally commented out in an effort to remind
#     you to change the URL it contains. It is recommended that you supply an
#     address/url where people can get help regarding session limits.

#SessionLimitDetailsLoc "Please visit http://your.website.url/ for more information about session limits."

# MaxSessionKill <number> [OPTIONAL]
#
# If given and different from 0, this option tells the Services to add an
# AKILL when there is number subsequent kills for the same hostname, preventing
# the network from KILL flood.

MaxSessionKill 15

# SessionAutoKillExpiry <time> [OPTIONAL]
#
# Sets the expiry time for autokills added for hosts that need to be
# AKILLed as controlled by the MaxSessionKill option. 
#
# If not given, the default value is 30 minutes.

SessionAutoKillExpiry 30m

# CheckClones <minusers> <maxdelay> <warningdelay>  [DEPRICATED]
#     Causes Services to try and detect "clones" connecting to the network.
#     A WALLOPS (or GOPER, if supported on the IRC server) will be sent if
#     Services thinks it has found clones.
#
#     This feature has been superceded by Session Limiting.
#
#     <minusers> sets the minimum number of users which must successively
#     connect to the network before Services will send a clone warning.
#
#     <maxdelay> sets the maximum time that can elapse between successive
#     users before Services decides they are not clones.
#
#     <warningdelay> sets the minimum time between clone warnings for
#     clones from the same host.
#
#     NOTE:  This option is not available when STREAMLINED is defined in
#     the Makefile.

# CheckClones   5 10s 30s

# KillClones [DISCOURAGED]  [DEPRICATED]
#     Causes Services to kill users which trigger the clone warnings.  (If
#     CheckClones is disabled, this will have no effect.)
#
#     This feature has been superceded by Session Limiting.
#
#     BEWARE!  The clone checking code is easily fooled; it can be
#     triggered falsely under many conditions, for example:
#
#         - Multiple users connecting from a shell machine.
#
#         - A single user repeatedly connecting and disconnecting.
#
#     Be very sure you know what you're doing before you even think about
#     enabling this option, and remember that Services comes with no
#     warranty.
#
#     If that wasn't enough discouragement:
#
#     ***** DO NOT ENABLE THIS OPTION! *****
#
#     NOTE:  This option is not available when STREAMLINED is defined in
#     the Makefile.

#KillClones
  


Comentários
[1] Comentário enviado por besk em 20/12/2004 - 12:19h

meio basico mas pronto

[2] Comentário enviado por slayffer em 24/06/2006 - 01:05h

vc nao poderia me arrumar uma conf do epona em Português,se puder manda um email para [email protected] ou [email protected]!!!

[3] Comentário enviado por gregorye em 24/06/2006 - 01:13h

bah amigo! não tem muito segredo, e caso queira é soh jogar em um tradutor e pimba! ateh o google tem tradutor! ;-)
q q coisa da um toque!

[4] Comentário enviado por slayffer em 27/06/2006 - 00:00h

vc poderia me dizer se existe tutorial desse services.conf ae que vc posto em portugues,é que tipo ta muito foda de configurar,FLWS


Contribuir com comentário