HdR
10.08.05, 16:25
Tag,
Unrealircd läuft, soweit ich beurteilen kann einwandfrei (kann schon connecten, usw.)
Nur die Services wollen nicht so recht zum irc-server connecten:
Auszug aus dem log:
[Aug 10 17:19:03.756515 2005] IRC Services 5.0.53 starting up (options: debug)
[Aug 10 17:19:03.756650 2005] debug: Loading language 0 from file `languages/en_us'
[Aug 10 17:19:03.757244 2005] debug: Loading language 10 from file `languages/nl'
[Aug 10 17:19:03.757851 2005] debug: Loading language 6 from file `languages/fr'
[Aug 10 17:19:03.758553 2005] debug: Loading language 9 from file `languages/de'
[Aug 10 17:19:03.759228 2005] debug: Loading language 11 from file `languages/hu'
[Aug 10 17:19:03.759886 2005] debug: Loading language 8 from file `languages/it'
[Aug 10 17:19:03.760185 2005] debug: Loading language 2 from file `languages/ja_euc'
[Aug 10 17:19:03.760744 2005] debug: Loading language 3 from file `languages/ja_sjis'
[Aug 10 17:19:03.761319 2005] debug: Loading language 5 from file `languages/pt'
[Aug 10 17:19:03.761685 2005] debug: Loading language 12 from file `languages/ru'
[Aug 10 17:19:03.762318 2005] debug: Loading language 4 from file `languages/es'
[Aug 10 17:19:03.763019 2005] debug: Loading language 7 from file `languages/tr'
[Aug 10 17:19:03.763714 2005] debug: Loaded languages
[Aug 10 17:19:03.763745 2005] debug: Loading module `protocol/unreal'
[Aug 10 17:19:03.765830 2005] debug: Successfully loaded module `protocol/unreal'
[Aug 10 17:19:03.765888 2005] debug: Loading module `database/version4'
[Aug 10 17:19:03.767440 2005] debug: Successfully loaded module `database/version4'
[Aug 10 17:19:03.767497 2005] debug: Loading module `encryption/md5'
[Aug 10 17:19:03.768196 2005] debug: Successfully loaded module `encryption/md5'
[Aug 10 17:19:03.768227 2005] debug: Loading module `operserv/main'
[Aug 10 17:19:03.768717 2005] debug: Successfully loaded module `operserv/main'
[Aug 10 17:19:03.768808 2005] debug: Loading module `operserv/akill'
[Aug 10 17:19:03.769154 2005] debug: Successfully loaded module `operserv/akill'
[Aug 10 17:19:03.769183 2005] debug: Loading module `operserv/news'
[Aug 10 17:19:03.769482 2005] debug: Successfully loaded module `operserv/news'
[Aug 10 17:19:03.769510 2005] debug: Loading module `operserv/sessions'
[Aug 10 17:19:03.769980 2005] debug: Successfully loaded module `operserv/sessions'
[Aug 10 17:19:03.770009 2005] debug: Loading module `operserv/sline'
[Aug 10 17:19:03.770432 2005] debug: Successfully loaded module `operserv/sline'
[Aug 10 17:19:03.770463 2005] debug: Loading module `nickserv/main'
[Aug 10 17:19:03.771359 2005] debug: Successfully loaded module `nickserv/main'
[Aug 10 17:19:03.771393 2005] debug: Loading module `nickserv/access'
[Aug 10 17:19:03.771836 2005] debug: Successfully loaded module `nickserv/access'
[Aug 10 17:19:03.771865 2005] debug: Loading module `nickserv/autojoin'
[Aug 10 17:19:03.772285 2005] debug: Successfully loaded module `nickserv/autojoin'
[Aug 10 17:19:03.772314 2005] debug: Loading module `nickserv/link'
[Aug 10 17:19:03.772867 2005] debug: Successfully loaded module `nickserv/link'
[Aug 10 17:19:03.772898 2005] debug: Loading module `chanserv/main'
[Aug 10 17:19:03.773935 2005] debug: Successfully loaded module `chanserv/main'
[Aug 10 17:19:03.773975 2005] debug: Loading module `chanserv/access-levels'
[Aug 10 17:19:03.774703 2005] debug: Successfully loaded module `chanserv/access-levels'
[Aug 10 17:19:03.774733 2005] debug: Loading module `statserv/main'
[Aug 10 17:19:03.775373 2005] debug: Successfully loaded module `statserv/main'
[Aug 10 17:19:03.775401 2005] debug: Loading module `misc/helpserv'
[Aug 10 17:19:03.776180 2005] debug: Successfully loaded module `misc/helpserv'
[Aug 10 17:19:03.776211 2005] debug: Loading module `misc/xml-export'
[Aug 10 17:19:03.776950 2005] debug: Successfully loaded module `misc/xml-export'
[Aug 10 17:19:03.776980 2005] debug: Loading module `misc/xml-import'
[Aug 10 17:19:03.777979 2005] debug: Successfully loaded module `misc/xml-import'
[Aug 10 17:19:03.778010 2005] debug: Loaded modules
[Aug 10 17:19:03.784511 2005] Initiated connection to 127.0.0.1:6667
[Aug 10 17:19:03.784717 2005] debug: Sent: PROTOCTL SJOIN SJOIN2 SJ3 NICKv2 VHP VL NOQUIT UMODE2 TOKEN NICKIP
[Aug 10 17:19:03.784747 2005] debug: Sent: PASS :xyz
[Aug 10 17:19:03.784772 2005] debug: Sent: SERVER services.localdomain 1 :U0-*-0 Services for IRC
[Aug 10 17:19:32.581838 2005] FATAL: Remote server returned: ERROR :Closing Link: [127.0.0.1] (Ping timeout)
unrealircd.conf:
loadmodule "src/modules/commands.so";
loadmodule "src/modules/cloak.so";
me {
name "85.10.198.207";
info "IRC-Server vom |DDC|Clan :: DeutscheDauerCamper";
numeric 1;
};
admin {
"Admin |DDC|HdR";
"hdr100@gmx.de";
"www.deutsche-dauer-camper.de";
};
class clients {
pingfreq 90;
maxclients 500;
sendq 100000;
recvq 8000;
};
class servers {
pingfreq 90;
maxclients 50;
sendq 1000000;
connfreq 100;
};
listen 127.0.0.1:6667;
listen 85.10.198.207:6668;
drpass {
restart "xyz";
die "xyz";
};
log "ircd.log" {
maxsize 2097152;
flags {
oper;
server-connects;
errors;
};
};
log "ircd.stuff.log" {
maxsize 2097152;
flags {
kline;
kills;
connects;
tkl;
};
};
oper admins {
class clients;
from {
userhost *@*;
};
password "xyz";
flags {
services-admin;
admin;
netadmin;
global;
can_rehash;
can_die;
can_restart;
can_wallops;
can_globops;
can_localroute;
can_globalroute;
can_globalkill;
can_kline;
can_gzline;
can_gkline;
can_unkline;
can_localnotice;
can_globalnotice;
can_zline;
get_umodew;
get_host;
can_override;
};
};
allow {
ip *@*;
hostname *@*;
class clients;
maxperip 3;
};
set {
kline-address "hdr100@gmx.de";
modes-on-connect "+x";
modes-on-oper "+xwgsfF";
snomask-on-oper "+sefG";
oper-auto-join "#services";
modes-on-join "+nt";
dns {
nameserver 127.0.0.1;
timeout 2s;
retries 2;
};
maxchannelsperuser 15;
anti-spam-quit-message-time 10s;
oper-only-stats "*okGvEOQCHYntTDd";
throttle {
connections 4;
period 60s;
};
anti-flood {
nick-flood 3:60;
unknown-flood-bantime 17s;
unknown-flood-amount 4000;
};
cloak-keys {
"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"boAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"coAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
};
};
set {
ident {
connect-timeout 19s;
read-timeout 40s;
};
network-name "DDC";
default-server "DDC";
services-server "services.localdomain";
help-channel "#Help";
hiddenhost-prefix "deutschedauercamper";
prefix-quit "Quit: pennen";
cloak-keys {
"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"boAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"coAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
};
hosts {
local "locop.localdomain";
global "ircop.localdomain";
coadmin "coadmin.localdomain";
admin "admin.localdomain";
servicesadmin "csop.localdomain";
netadmin "netadmin.localdomain";
host-on-oper-up "no";
};
};
link services.localdomain {
username *;
hostname 127.0.0.1;
bind-ip *;
port 6667;
password-connect "xyz";
password-receive "xyz";
class servers;
};
ulines {
services.localdomain;
};
tld {
mask *@*;
motd "motd.conf";
rules "rules.conf";
};
ircservices.conf:
# Example configuration file for Services.
# 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).
# Make sure to uncomment the directive (remove the leading "#") before
# running Services.
#
# 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 127.0.0.1 6667 "xyz"
# 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.
#LocalAddress 85.10.198.207 6602
#LocalAddress host.name.here 6677
################################################## #########################
#
# Services identification
#
################################################## #########################
# ServerName <name> [REQUIRED]
# Specifies the IRC server name which Services should use when it
# connects to the network.
ServerName "services.localdomain"
#ServerName "127.0.0.1"
# ServerDesc <text> [REQUIRED]
# Specifies the text which should appear as the server's information in
# /whois and similar queries.
ServerDesc "Services for IRC"
# ServiceUser <usermask> [REQUIRED]
# Specifies the user@host mask which should be used by the Services
# pseudoclients.
ServiceUser "services@localdomain"
################################################## #########################
#
# Unix group and umask to use
#
################################################## #########################
# RunGroup <group> [OPTIONAL]
# Specify the group which Services should run as. <group> can be
# either a group name or an equals sign ("=") followed by a group ID.
# If not specified, Services will use the group ID it is started with.
# Note that Unix setgid permission on the executable file will do the
# same thing, but the setgid permission bit is cleared whenever the
# file is modified, while this setting will always be used (if the
# system permits it) when Services is started.
#RunGroup services
#RunGroup =65534 # A common value for the "nogroup" group
# Umask <umask> [RECOMMENDED]
# Sets the umask (file creation mask) for Services. This mask is
# applied to all data files created by Services, including database
# files (which are recreated on every database update) and the process
# ID file (PIDFilename, below), and indicates which file permission
# bits are NOT to be set on those files as an octal value. Common
# values are given in the examples below. If not specified, the umask
# in place when Services is started will be used.
Umask 077 # Disallows access to all but file owner
# (recommended when RunGroup is not set)
#Umask 007 # Allows access to members of file group as well
# (recommended when RunGroup is set)
################################################## #########################
#
# Services data filenames
#
################################################## #########################
# NOTE: All filenames are relative to the Services data directory.
# LogFilename <filename> [REQUIRED]
# Specifies the name of the file into which Services will log data.
# May be overridden by the -log command-line option. If this name
# contains "%y", "%m", or "%d", they will be replaced by the current
# year, month, or day, respectively, and the logfile will be
# automatically rotated as needed when the date changes.
LogFilename ircservices.log
# PIDFilename <filename> [REQUIRED]
# Specifies the name of the file containing Services' process ID.
# Note that if you change this filename, and you are using the
# "ircservices-chk" crontab script provided with Services, you will
# need to change the filename in that file as well.
PIDFilename ircservices.pid
# MOTDFilename <filename> [REQUIRED]
# Specifies the name of the Message of the Day file.
MOTDFilename ircservices.motd
# LockFilename <filename> [REQUIRED]
# Specifies the name of the data directory lock file. This file is
# created in the data directory when Services begins updating
# databases, and is removed after the databases are updated. If the
# file already exists when Services tries to update the databases,
# Services sends a warning (via wallops) and does not write any data.
LockFilename .lock
################################################## #########################
#
# Basic functionality
#
################################################## #########################
# NoBouncyModes [OPTIONAL]
# Normally, Services will check for the remote IRC server reversing its
# mode changes, and issue a warning (and stop changing modes) if it
# detects such a problem. However, the detection will sometimes
# trigger even when there is no problem, thus preventing channel
# mode-locks and other features from working. If you specify this
# directive, Services will not check for mode bouncing, which can avoid
# this problem if you know your servers are set up correctly.
#
# WARNING: setting this option when your servers are incorrectly
# configured can result in flooding!
#NoBouncyModes
# NoSplitRecovery [OPTIONAL]
# Disables Services' recognition of users returning from netsplits.
# Normally (on networks with some sort of timestamp support in the IRC
# server), Services will check via the timestamp field whether a user
# is the same as the last user who identified for the nick, and allow
# the user access to that nick without requiring identification again
# if the timestamps match. Enabling this directive will force all
# users to re-identify after a netsplit.
#
# It's generally easier on users to leave this disabled, but if you
# suspect one of your servers has been hacked to send false timestamps
# (or you suspect a bug in Services itself) enabling this directive
# will eliminate the possibility of one user "stealing" another's nick
# by pretending to have the same timestamp.
#
# You may also want to uncomment this directive if your servers' clocks
# are very far apart; the less synchronized the servers' clocks are,
# the greater the possibility of someone "taking over" another person's
# nick when a server with a fast clock splits.
#
# NOTE: On DALnet 4.4.15+, Dreamforge, Bahamut, Unreal, and compatible
# networks, Services takes advantage of an IRC server feature to assign
# each user a permanent ID number, which significantly enhances the
# security of this check. On such networks, you should almost always
# leave this directive commented out. See section 3-1-2 of the manual
# for details.
#NoSplitRecovery
# 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 (subject 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).
# Note that entering a correct password will _not_ reset this count.
BadPassLimit 5
# 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
# BadPassWarning <count> [RECOMMENDED]
# Sets the number of bad passwords _for a single nick or channel_ that
# will be accepted before a warning is sent using WALLOPS/GLOBOPS. If
# not given, no warnings will be sent.
BadPassWarning 5
# UpdateTimeout <time> [REQUIRED]
# Sets the delay between automatic database updates. This timer is
# reset by the OperServ UPDATE command.
UpdateTimeout 5m
# ExpireTimeout <time> [DEPRECATED]
# Formerly used to set the delay between checks for expired nicknames
# and channels. As expiration is now checked for whenever a nickname
# or channel is accessed, this directive now serves no function, and
# is therefore deprecated; it will be removed in the next version of
# Services.
#ExpireTimeout 30m
# WarningTimeout <time> [REQUIRED]
# Sets the interval between sending warning messages for program
# errors via WALLOPS/GLOBOPS.
WarningTimeout 4h
# ReadTimeout <seconds> [REQUIRED]
# Sets the timeout period for reading from the network; this is the
# length of time Services will wait to receive data from an external
# source if none is available before proceeding with other actions,
# such as timeout checking. Note that the parameter is a number of
# seconds, not a "time"; it may also include a fractional part, such as
# "0.5".
#
# This value also influences the period between timeout checks; see the
# TimeoutCheck directive below.
ReadTimeout 3
# TimeoutCheck <seconds> [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. Note that the parameter is a
# number of seconds, not a "time", and may include a fractional part.
#
# This shouldn't be set any higher than 10 seconds, and 1 second or
# less 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 provides the most accurate
# timeout response but may require too much processing on large
# networks.
#
# Note that if this value is smaller than ReadTimeout (above), then the
# delay between checks of the timeout list may exceed the value given
# here during periods of little or no network activity.
TimeoutCheck 1.0
# PingFrequency <time> [OPTIONAL]
# Sets the time after which Services sends a PING message to its uplink
# if no other network activity has occurred. This can be useful if you
# have a low-activity network and your server keeps dropping Services'
# connection with "Ping timeout". If not set, Services will not send
# PING messages.
#PingFrequency 30s
# MergeChannelModes <seconds> [OPTIONAL]
# WARNING: This directive can have security implications; read
# carefully before enabling.
#
# If this directive is given, it causes Services to not send out
# channel mode changes immediately, but to wait for the given number of
# seconds (which may be fractional) and collect all channel modes to
# send in a single command. For example, if two users enter a channel
# at nearly the same time and both of them are to be opped, instead of
# sending two MODE +o commands, Services will send a single MODE +oo
# command. This option can help with large channels in reducing mode
# floods, particularly when Services first connects or a server
# reconnects after a split; however, the sending of the mode command
# will be slightly delayed, so that the users will have to wait a short
# time before getting chanop privileges. Furthermore, since this
# increases the time before deops, etc. occur, users can take advantage
# of netsplits to "steal ops" for a short time before Services responds.
#
# Services will never send out more than six parameters with each MODE
# command (this limit is part of the IRC protocol specification). If
# more than six +o, +v, etc. modes are to be sent, Services will send
# them out six at a time without waiting for the timeout given with
# this directive. Also, if more than MERGE_CHANMODE_SLOTS (defined in
# config.h; default 3) channels receive modes before the timeout
# expires, those modes will similarly be sent out at that time.
#
# Note that the actual sending of the MODE command may be delayed by as
# much as the TimeoutCheck value; if you use this option, then in
# general you should set TimeoutCheck to the same (or a smaller) value.
# Also, on networks with little traffic there may be an additional
# delay up to the value of ReadTimeout before the modes are sent.
#
# If this option is not set, Services will still collect all mode changes
# resulting from a single event (such as a user joining a channel) and
# send them in a single message as soon as the event processing finishes.
#MergeChannelModes 0.5
# NetBufferSize <total-size> [<per-connection-size>] [RECOMMENDED]
# Sets the maximum amount of memory used by network connection buffers.
# If a second parameter is given, it sets the maximum amount of memory
# used by a single connection; if not given, this defaults to the same
# as the total limit.
NetBufferSize 4194304 1048576 # 4MB and 1MB
# NetBufferLimit <inactive-limit> [<ignore-limit>] [RECOMMENDED]
# Sets the threshold at which Services sends a "busy" reply to PRIVMSGs
# (<inactive-limit>) and at which Services ignores PRIVMSGs entirely
# (<ignore-limit>). Both thresholds apply to non-operator users only;
# PRIVMSGs from IRC operators will always be processed normally. A
# WALLOPS/GLOBOPS message will be sent when Services exceeds or drops
# below either of the thresholds. If the thresholds are set to the
# same value, "busy" messages will never be sent.
#
# The thresholds are expressed as percentages of the value(s) given for
# NetBufferSize above. If both a total size limit and a per-connection
# size limit are specified, the higher of the two percentages is
# checked against these thresholds.
#
# If NetBufferSize is not specified, NetBufferLimit has no effect.
NetBufferLimit 80 95
################################################## #########################
#
# Miscellaneous settings
#
################################################## #########################
# These are settings which don't belong anywhere else, or which would
# be module settings but apply to multiple modules.
# GuestNickPrefix <value> [REQUIRED]
# Sets the nickname prefix used when Services changes a user's
# nickname (for example, from the "NSForceNickChange" NickServ option).
# A unique series of digits will be appended to this string to form the
# new nickname. This option is ignored for IRC servers which do not
# allow remote clients' nicknames to be forcibly changed, but it must
# be set to something anyway.
GuestNickPrefix "Guest"
# DefTimeZone <time-zone> [OPTIONAL]
# Sets the time zone to be used for displaying the time of day with
# certain commands, such as NickServ INFO. If not given, the system's
# default time zone (the value of the TZ environment variable) is used.
# <time-zone> is the name of the time zone to be used; consult your
# system manual for how time zone names are specified on your system.
# Note that users can set time zones for their own nicknames
# independently; this setting is only used as a default. The
# following example will cause Services to use United States Pacific
# time on most systems:
#DefTimeZone PST8PDT
# LogMaxUsers [OPTIONAL]
# Causes Services to write a message to the log every time a new
# user maximum is reached.
LogMaxUsers
# EnableGetpass [OPTIONAL]
# Allows use of the NickServ and ChanServ GETPASS commands.
EnableGetpass
# 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
################################################## #########################
# Base IRC protocol module [REQUIRED]
# These modules provide the base functionality for communicating with
# the remote IRC server, and MUST be loaded before any other module.
# Select the module which matches the IRC server you are using:
# protocol/bahamut DALnet Bahamut server, versions 1.4.25+
# protocol/dalnet DALnet server, version 4.4.13 and earlier
# protocol/dreamforge DALnet Dreamforge server, versions 4.4.15+
# protocol/hybrid Hybrid server, version 7.0
# protocol/monkey Chunky Monkey IRCD, version 1.0 and later
# protocol/ptlink PTlink IRC server, version 6.0 and later
# protocol/rfc1459 RFC1459-compliant servers
# protocol/trircd Trircd server, version 4.0 and later
# protocol/ts8 RFC1459 with TS8 extensions
# protocol/undernet-p9 Undernet server, version 2.9.x only
# protocol/unreal Unreal server, version 3.1.0 and later
# Modules marked with are still in an experimental stage and may
# not be stable.
LoadModule protocol/unreal
################################################## #########################
# Database access module [REQUIRED]
# These modules provide access to permanent storage for data used by
# various Services modules, and MUST be loaded before any other module
# (except protocol and encryption modules). Select the module
# corresponding to the type of database you want to use:
# database/version4 Database files compatible with version
# 4.5.x of Services
LoadModule database/version4
LoadModule encryption/md5
################################################## #########################
# Mail-sending modules [OPTIONAL]
# This set of modules allows Services to send E-mail. This feature is
# currently used to forward memos via E-mail and implement E-mail
# address confirmation. Two modules must be loaded to use mail, the
# main module (mail/main) and one of the following low-level modules:
# mail/smtp [RECOMMENDED]
# Sends mail via the SMTP protocol.
# mail/sendmail [DISCOURAGED]
# Sends mail via a "sendmail" program. This module should
# not be used unless you cannot send mail via SMTP.
#LoadModule mail/main
#LoadModule mail/smtp
#LoadModule mail/sendmail
################################################## #########################
# OperServ modules [RECOMMENDED]
LoadModule operserv/main
LoadModule operserv/akill
LoadModule operserv/news
LoadModule operserv/sessions
LoadModule operserv/sline
################################################## #########################
# NickServ modules [RECOMMENDED]
LoadModule nickserv/main
LoadModule nickserv/access
LoadModule nickserv/autojoin
LoadModule nickserv/link
#LoadModule nickserv/mail-auth
#LoadModule nickserv/oldlink
#LoadModule nickserv/sendpass
################################################## #########################
# ChanServ modules [RECOMMENDED]
LoadModule chanserv/main
LoadModule chanserv/access-levels
#LoadModule chanserv/access-xop
#LoadModule chanserv/sendpass
################################################## #########################
# MemoServ modules [RECOMMENDED]
# LoadModule memoserv/main
# LoadModule memoserv/forward
# LoadModule memoserv/ignore
################################################## #########################
# StatServ modules [OPTIONAL]
LoadModule statserv/main
################################################## #########################
# HelpServ module [OPTIONAL]
LoadModule misc/helpserv
################################################## #########################
# HTTP server modules [OPTIONAL]
#LoadModule httpd/main
#LoadModule httpd/auth-ip
#LoadModule httpd/auth-password
#LoadModule httpd/dbaccess
#LoadModule httpd/debug
#LoadModule httpd/redirect
#LoadModule httpd/top-page
################################################## #########################
LoadModule misc/xml-export
LoadModule misc/xml-import
################################################## #########################
# End of example-ircservices.conf
Unrealircd läuft, soweit ich beurteilen kann einwandfrei (kann schon connecten, usw.)
Nur die Services wollen nicht so recht zum irc-server connecten:
Auszug aus dem log:
[Aug 10 17:19:03.756515 2005] IRC Services 5.0.53 starting up (options: debug)
[Aug 10 17:19:03.756650 2005] debug: Loading language 0 from file `languages/en_us'
[Aug 10 17:19:03.757244 2005] debug: Loading language 10 from file `languages/nl'
[Aug 10 17:19:03.757851 2005] debug: Loading language 6 from file `languages/fr'
[Aug 10 17:19:03.758553 2005] debug: Loading language 9 from file `languages/de'
[Aug 10 17:19:03.759228 2005] debug: Loading language 11 from file `languages/hu'
[Aug 10 17:19:03.759886 2005] debug: Loading language 8 from file `languages/it'
[Aug 10 17:19:03.760185 2005] debug: Loading language 2 from file `languages/ja_euc'
[Aug 10 17:19:03.760744 2005] debug: Loading language 3 from file `languages/ja_sjis'
[Aug 10 17:19:03.761319 2005] debug: Loading language 5 from file `languages/pt'
[Aug 10 17:19:03.761685 2005] debug: Loading language 12 from file `languages/ru'
[Aug 10 17:19:03.762318 2005] debug: Loading language 4 from file `languages/es'
[Aug 10 17:19:03.763019 2005] debug: Loading language 7 from file `languages/tr'
[Aug 10 17:19:03.763714 2005] debug: Loaded languages
[Aug 10 17:19:03.763745 2005] debug: Loading module `protocol/unreal'
[Aug 10 17:19:03.765830 2005] debug: Successfully loaded module `protocol/unreal'
[Aug 10 17:19:03.765888 2005] debug: Loading module `database/version4'
[Aug 10 17:19:03.767440 2005] debug: Successfully loaded module `database/version4'
[Aug 10 17:19:03.767497 2005] debug: Loading module `encryption/md5'
[Aug 10 17:19:03.768196 2005] debug: Successfully loaded module `encryption/md5'
[Aug 10 17:19:03.768227 2005] debug: Loading module `operserv/main'
[Aug 10 17:19:03.768717 2005] debug: Successfully loaded module `operserv/main'
[Aug 10 17:19:03.768808 2005] debug: Loading module `operserv/akill'
[Aug 10 17:19:03.769154 2005] debug: Successfully loaded module `operserv/akill'
[Aug 10 17:19:03.769183 2005] debug: Loading module `operserv/news'
[Aug 10 17:19:03.769482 2005] debug: Successfully loaded module `operserv/news'
[Aug 10 17:19:03.769510 2005] debug: Loading module `operserv/sessions'
[Aug 10 17:19:03.769980 2005] debug: Successfully loaded module `operserv/sessions'
[Aug 10 17:19:03.770009 2005] debug: Loading module `operserv/sline'
[Aug 10 17:19:03.770432 2005] debug: Successfully loaded module `operserv/sline'
[Aug 10 17:19:03.770463 2005] debug: Loading module `nickserv/main'
[Aug 10 17:19:03.771359 2005] debug: Successfully loaded module `nickserv/main'
[Aug 10 17:19:03.771393 2005] debug: Loading module `nickserv/access'
[Aug 10 17:19:03.771836 2005] debug: Successfully loaded module `nickserv/access'
[Aug 10 17:19:03.771865 2005] debug: Loading module `nickserv/autojoin'
[Aug 10 17:19:03.772285 2005] debug: Successfully loaded module `nickserv/autojoin'
[Aug 10 17:19:03.772314 2005] debug: Loading module `nickserv/link'
[Aug 10 17:19:03.772867 2005] debug: Successfully loaded module `nickserv/link'
[Aug 10 17:19:03.772898 2005] debug: Loading module `chanserv/main'
[Aug 10 17:19:03.773935 2005] debug: Successfully loaded module `chanserv/main'
[Aug 10 17:19:03.773975 2005] debug: Loading module `chanserv/access-levels'
[Aug 10 17:19:03.774703 2005] debug: Successfully loaded module `chanserv/access-levels'
[Aug 10 17:19:03.774733 2005] debug: Loading module `statserv/main'
[Aug 10 17:19:03.775373 2005] debug: Successfully loaded module `statserv/main'
[Aug 10 17:19:03.775401 2005] debug: Loading module `misc/helpserv'
[Aug 10 17:19:03.776180 2005] debug: Successfully loaded module `misc/helpserv'
[Aug 10 17:19:03.776211 2005] debug: Loading module `misc/xml-export'
[Aug 10 17:19:03.776950 2005] debug: Successfully loaded module `misc/xml-export'
[Aug 10 17:19:03.776980 2005] debug: Loading module `misc/xml-import'
[Aug 10 17:19:03.777979 2005] debug: Successfully loaded module `misc/xml-import'
[Aug 10 17:19:03.778010 2005] debug: Loaded modules
[Aug 10 17:19:03.784511 2005] Initiated connection to 127.0.0.1:6667
[Aug 10 17:19:03.784717 2005] debug: Sent: PROTOCTL SJOIN SJOIN2 SJ3 NICKv2 VHP VL NOQUIT UMODE2 TOKEN NICKIP
[Aug 10 17:19:03.784747 2005] debug: Sent: PASS :xyz
[Aug 10 17:19:03.784772 2005] debug: Sent: SERVER services.localdomain 1 :U0-*-0 Services for IRC
[Aug 10 17:19:32.581838 2005] FATAL: Remote server returned: ERROR :Closing Link: [127.0.0.1] (Ping timeout)
unrealircd.conf:
loadmodule "src/modules/commands.so";
loadmodule "src/modules/cloak.so";
me {
name "85.10.198.207";
info "IRC-Server vom |DDC|Clan :: DeutscheDauerCamper";
numeric 1;
};
admin {
"Admin |DDC|HdR";
"hdr100@gmx.de";
"www.deutsche-dauer-camper.de";
};
class clients {
pingfreq 90;
maxclients 500;
sendq 100000;
recvq 8000;
};
class servers {
pingfreq 90;
maxclients 50;
sendq 1000000;
connfreq 100;
};
listen 127.0.0.1:6667;
listen 85.10.198.207:6668;
drpass {
restart "xyz";
die "xyz";
};
log "ircd.log" {
maxsize 2097152;
flags {
oper;
server-connects;
errors;
};
};
log "ircd.stuff.log" {
maxsize 2097152;
flags {
kline;
kills;
connects;
tkl;
};
};
oper admins {
class clients;
from {
userhost *@*;
};
password "xyz";
flags {
services-admin;
admin;
netadmin;
global;
can_rehash;
can_die;
can_restart;
can_wallops;
can_globops;
can_localroute;
can_globalroute;
can_globalkill;
can_kline;
can_gzline;
can_gkline;
can_unkline;
can_localnotice;
can_globalnotice;
can_zline;
get_umodew;
get_host;
can_override;
};
};
allow {
ip *@*;
hostname *@*;
class clients;
maxperip 3;
};
set {
kline-address "hdr100@gmx.de";
modes-on-connect "+x";
modes-on-oper "+xwgsfF";
snomask-on-oper "+sefG";
oper-auto-join "#services";
modes-on-join "+nt";
dns {
nameserver 127.0.0.1;
timeout 2s;
retries 2;
};
maxchannelsperuser 15;
anti-spam-quit-message-time 10s;
oper-only-stats "*okGvEOQCHYntTDd";
throttle {
connections 4;
period 60s;
};
anti-flood {
nick-flood 3:60;
unknown-flood-bantime 17s;
unknown-flood-amount 4000;
};
cloak-keys {
"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"boAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"coAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
};
};
set {
ident {
connect-timeout 19s;
read-timeout 40s;
};
network-name "DDC";
default-server "DDC";
services-server "services.localdomain";
help-channel "#Help";
hiddenhost-prefix "deutschedauercamper";
prefix-quit "Quit: pennen";
cloak-keys {
"aoAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"boAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
"coAr1HnR6gl3sJ7hVz4Zb7x4YwpW";
};
hosts {
local "locop.localdomain";
global "ircop.localdomain";
coadmin "coadmin.localdomain";
admin "admin.localdomain";
servicesadmin "csop.localdomain";
netadmin "netadmin.localdomain";
host-on-oper-up "no";
};
};
link services.localdomain {
username *;
hostname 127.0.0.1;
bind-ip *;
port 6667;
password-connect "xyz";
password-receive "xyz";
class servers;
};
ulines {
services.localdomain;
};
tld {
mask *@*;
motd "motd.conf";
rules "rules.conf";
};
ircservices.conf:
# Example configuration file for Services.
# 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).
# Make sure to uncomment the directive (remove the leading "#") before
# running Services.
#
# 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 127.0.0.1 6667 "xyz"
# 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.
#LocalAddress 85.10.198.207 6602
#LocalAddress host.name.here 6677
################################################## #########################
#
# Services identification
#
################################################## #########################
# ServerName <name> [REQUIRED]
# Specifies the IRC server name which Services should use when it
# connects to the network.
ServerName "services.localdomain"
#ServerName "127.0.0.1"
# ServerDesc <text> [REQUIRED]
# Specifies the text which should appear as the server's information in
# /whois and similar queries.
ServerDesc "Services for IRC"
# ServiceUser <usermask> [REQUIRED]
# Specifies the user@host mask which should be used by the Services
# pseudoclients.
ServiceUser "services@localdomain"
################################################## #########################
#
# Unix group and umask to use
#
################################################## #########################
# RunGroup <group> [OPTIONAL]
# Specify the group which Services should run as. <group> can be
# either a group name or an equals sign ("=") followed by a group ID.
# If not specified, Services will use the group ID it is started with.
# Note that Unix setgid permission on the executable file will do the
# same thing, but the setgid permission bit is cleared whenever the
# file is modified, while this setting will always be used (if the
# system permits it) when Services is started.
#RunGroup services
#RunGroup =65534 # A common value for the "nogroup" group
# Umask <umask> [RECOMMENDED]
# Sets the umask (file creation mask) for Services. This mask is
# applied to all data files created by Services, including database
# files (which are recreated on every database update) and the process
# ID file (PIDFilename, below), and indicates which file permission
# bits are NOT to be set on those files as an octal value. Common
# values are given in the examples below. If not specified, the umask
# in place when Services is started will be used.
Umask 077 # Disallows access to all but file owner
# (recommended when RunGroup is not set)
#Umask 007 # Allows access to members of file group as well
# (recommended when RunGroup is set)
################################################## #########################
#
# Services data filenames
#
################################################## #########################
# NOTE: All filenames are relative to the Services data directory.
# LogFilename <filename> [REQUIRED]
# Specifies the name of the file into which Services will log data.
# May be overridden by the -log command-line option. If this name
# contains "%y", "%m", or "%d", they will be replaced by the current
# year, month, or day, respectively, and the logfile will be
# automatically rotated as needed when the date changes.
LogFilename ircservices.log
# PIDFilename <filename> [REQUIRED]
# Specifies the name of the file containing Services' process ID.
# Note that if you change this filename, and you are using the
# "ircservices-chk" crontab script provided with Services, you will
# need to change the filename in that file as well.
PIDFilename ircservices.pid
# MOTDFilename <filename> [REQUIRED]
# Specifies the name of the Message of the Day file.
MOTDFilename ircservices.motd
# LockFilename <filename> [REQUIRED]
# Specifies the name of the data directory lock file. This file is
# created in the data directory when Services begins updating
# databases, and is removed after the databases are updated. If the
# file already exists when Services tries to update the databases,
# Services sends a warning (via wallops) and does not write any data.
LockFilename .lock
################################################## #########################
#
# Basic functionality
#
################################################## #########################
# NoBouncyModes [OPTIONAL]
# Normally, Services will check for the remote IRC server reversing its
# mode changes, and issue a warning (and stop changing modes) if it
# detects such a problem. However, the detection will sometimes
# trigger even when there is no problem, thus preventing channel
# mode-locks and other features from working. If you specify this
# directive, Services will not check for mode bouncing, which can avoid
# this problem if you know your servers are set up correctly.
#
# WARNING: setting this option when your servers are incorrectly
# configured can result in flooding!
#NoBouncyModes
# NoSplitRecovery [OPTIONAL]
# Disables Services' recognition of users returning from netsplits.
# Normally (on networks with some sort of timestamp support in the IRC
# server), Services will check via the timestamp field whether a user
# is the same as the last user who identified for the nick, and allow
# the user access to that nick without requiring identification again
# if the timestamps match. Enabling this directive will force all
# users to re-identify after a netsplit.
#
# It's generally easier on users to leave this disabled, but if you
# suspect one of your servers has been hacked to send false timestamps
# (or you suspect a bug in Services itself) enabling this directive
# will eliminate the possibility of one user "stealing" another's nick
# by pretending to have the same timestamp.
#
# You may also want to uncomment this directive if your servers' clocks
# are very far apart; the less synchronized the servers' clocks are,
# the greater the possibility of someone "taking over" another person's
# nick when a server with a fast clock splits.
#
# NOTE: On DALnet 4.4.15+, Dreamforge, Bahamut, Unreal, and compatible
# networks, Services takes advantage of an IRC server feature to assign
# each user a permanent ID number, which significantly enhances the
# security of this check. On such networks, you should almost always
# leave this directive commented out. See section 3-1-2 of the manual
# for details.
#NoSplitRecovery
# 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 (subject 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).
# Note that entering a correct password will _not_ reset this count.
BadPassLimit 5
# 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
# BadPassWarning <count> [RECOMMENDED]
# Sets the number of bad passwords _for a single nick or channel_ that
# will be accepted before a warning is sent using WALLOPS/GLOBOPS. If
# not given, no warnings will be sent.
BadPassWarning 5
# UpdateTimeout <time> [REQUIRED]
# Sets the delay between automatic database updates. This timer is
# reset by the OperServ UPDATE command.
UpdateTimeout 5m
# ExpireTimeout <time> [DEPRECATED]
# Formerly used to set the delay between checks for expired nicknames
# and channels. As expiration is now checked for whenever a nickname
# or channel is accessed, this directive now serves no function, and
# is therefore deprecated; it will be removed in the next version of
# Services.
#ExpireTimeout 30m
# WarningTimeout <time> [REQUIRED]
# Sets the interval between sending warning messages for program
# errors via WALLOPS/GLOBOPS.
WarningTimeout 4h
# ReadTimeout <seconds> [REQUIRED]
# Sets the timeout period for reading from the network; this is the
# length of time Services will wait to receive data from an external
# source if none is available before proceeding with other actions,
# such as timeout checking. Note that the parameter is a number of
# seconds, not a "time"; it may also include a fractional part, such as
# "0.5".
#
# This value also influences the period between timeout checks; see the
# TimeoutCheck directive below.
ReadTimeout 3
# TimeoutCheck <seconds> [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. Note that the parameter is a
# number of seconds, not a "time", and may include a fractional part.
#
# This shouldn't be set any higher than 10 seconds, and 1 second or
# less 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 provides the most accurate
# timeout response but may require too much processing on large
# networks.
#
# Note that if this value is smaller than ReadTimeout (above), then the
# delay between checks of the timeout list may exceed the value given
# here during periods of little or no network activity.
TimeoutCheck 1.0
# PingFrequency <time> [OPTIONAL]
# Sets the time after which Services sends a PING message to its uplink
# if no other network activity has occurred. This can be useful if you
# have a low-activity network and your server keeps dropping Services'
# connection with "Ping timeout". If not set, Services will not send
# PING messages.
#PingFrequency 30s
# MergeChannelModes <seconds> [OPTIONAL]
# WARNING: This directive can have security implications; read
# carefully before enabling.
#
# If this directive is given, it causes Services to not send out
# channel mode changes immediately, but to wait for the given number of
# seconds (which may be fractional) and collect all channel modes to
# send in a single command. For example, if two users enter a channel
# at nearly the same time and both of them are to be opped, instead of
# sending two MODE +o commands, Services will send a single MODE +oo
# command. This option can help with large channels in reducing mode
# floods, particularly when Services first connects or a server
# reconnects after a split; however, the sending of the mode command
# will be slightly delayed, so that the users will have to wait a short
# time before getting chanop privileges. Furthermore, since this
# increases the time before deops, etc. occur, users can take advantage
# of netsplits to "steal ops" for a short time before Services responds.
#
# Services will never send out more than six parameters with each MODE
# command (this limit is part of the IRC protocol specification). If
# more than six +o, +v, etc. modes are to be sent, Services will send
# them out six at a time without waiting for the timeout given with
# this directive. Also, if more than MERGE_CHANMODE_SLOTS (defined in
# config.h; default 3) channels receive modes before the timeout
# expires, those modes will similarly be sent out at that time.
#
# Note that the actual sending of the MODE command may be delayed by as
# much as the TimeoutCheck value; if you use this option, then in
# general you should set TimeoutCheck to the same (or a smaller) value.
# Also, on networks with little traffic there may be an additional
# delay up to the value of ReadTimeout before the modes are sent.
#
# If this option is not set, Services will still collect all mode changes
# resulting from a single event (such as a user joining a channel) and
# send them in a single message as soon as the event processing finishes.
#MergeChannelModes 0.5
# NetBufferSize <total-size> [<per-connection-size>] [RECOMMENDED]
# Sets the maximum amount of memory used by network connection buffers.
# If a second parameter is given, it sets the maximum amount of memory
# used by a single connection; if not given, this defaults to the same
# as the total limit.
NetBufferSize 4194304 1048576 # 4MB and 1MB
# NetBufferLimit <inactive-limit> [<ignore-limit>] [RECOMMENDED]
# Sets the threshold at which Services sends a "busy" reply to PRIVMSGs
# (<inactive-limit>) and at which Services ignores PRIVMSGs entirely
# (<ignore-limit>). Both thresholds apply to non-operator users only;
# PRIVMSGs from IRC operators will always be processed normally. A
# WALLOPS/GLOBOPS message will be sent when Services exceeds or drops
# below either of the thresholds. If the thresholds are set to the
# same value, "busy" messages will never be sent.
#
# The thresholds are expressed as percentages of the value(s) given for
# NetBufferSize above. If both a total size limit and a per-connection
# size limit are specified, the higher of the two percentages is
# checked against these thresholds.
#
# If NetBufferSize is not specified, NetBufferLimit has no effect.
NetBufferLimit 80 95
################################################## #########################
#
# Miscellaneous settings
#
################################################## #########################
# These are settings which don't belong anywhere else, or which would
# be module settings but apply to multiple modules.
# GuestNickPrefix <value> [REQUIRED]
# Sets the nickname prefix used when Services changes a user's
# nickname (for example, from the "NSForceNickChange" NickServ option).
# A unique series of digits will be appended to this string to form the
# new nickname. This option is ignored for IRC servers which do not
# allow remote clients' nicknames to be forcibly changed, but it must
# be set to something anyway.
GuestNickPrefix "Guest"
# DefTimeZone <time-zone> [OPTIONAL]
# Sets the time zone to be used for displaying the time of day with
# certain commands, such as NickServ INFO. If not given, the system's
# default time zone (the value of the TZ environment variable) is used.
# <time-zone> is the name of the time zone to be used; consult your
# system manual for how time zone names are specified on your system.
# Note that users can set time zones for their own nicknames
# independently; this setting is only used as a default. The
# following example will cause Services to use United States Pacific
# time on most systems:
#DefTimeZone PST8PDT
# LogMaxUsers [OPTIONAL]
# Causes Services to write a message to the log every time a new
# user maximum is reached.
LogMaxUsers
# EnableGetpass [OPTIONAL]
# Allows use of the NickServ and ChanServ GETPASS commands.
EnableGetpass
# 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
################################################## #########################
# Base IRC protocol module [REQUIRED]
# These modules provide the base functionality for communicating with
# the remote IRC server, and MUST be loaded before any other module.
# Select the module which matches the IRC server you are using:
# protocol/bahamut DALnet Bahamut server, versions 1.4.25+
# protocol/dalnet DALnet server, version 4.4.13 and earlier
# protocol/dreamforge DALnet Dreamforge server, versions 4.4.15+
# protocol/hybrid Hybrid server, version 7.0
# protocol/monkey Chunky Monkey IRCD, version 1.0 and later
# protocol/ptlink PTlink IRC server, version 6.0 and later
# protocol/rfc1459 RFC1459-compliant servers
# protocol/trircd Trircd server, version 4.0 and later
# protocol/ts8 RFC1459 with TS8 extensions
# protocol/undernet-p9 Undernet server, version 2.9.x only
# protocol/unreal Unreal server, version 3.1.0 and later
# Modules marked with are still in an experimental stage and may
# not be stable.
LoadModule protocol/unreal
################################################## #########################
# Database access module [REQUIRED]
# These modules provide access to permanent storage for data used by
# various Services modules, and MUST be loaded before any other module
# (except protocol and encryption modules). Select the module
# corresponding to the type of database you want to use:
# database/version4 Database files compatible with version
# 4.5.x of Services
LoadModule database/version4
LoadModule encryption/md5
################################################## #########################
# Mail-sending modules [OPTIONAL]
# This set of modules allows Services to send E-mail. This feature is
# currently used to forward memos via E-mail and implement E-mail
# address confirmation. Two modules must be loaded to use mail, the
# main module (mail/main) and one of the following low-level modules:
# mail/smtp [RECOMMENDED]
# Sends mail via the SMTP protocol.
# mail/sendmail [DISCOURAGED]
# Sends mail via a "sendmail" program. This module should
# not be used unless you cannot send mail via SMTP.
#LoadModule mail/main
#LoadModule mail/smtp
#LoadModule mail/sendmail
################################################## #########################
# OperServ modules [RECOMMENDED]
LoadModule operserv/main
LoadModule operserv/akill
LoadModule operserv/news
LoadModule operserv/sessions
LoadModule operserv/sline
################################################## #########################
# NickServ modules [RECOMMENDED]
LoadModule nickserv/main
LoadModule nickserv/access
LoadModule nickserv/autojoin
LoadModule nickserv/link
#LoadModule nickserv/mail-auth
#LoadModule nickserv/oldlink
#LoadModule nickserv/sendpass
################################################## #########################
# ChanServ modules [RECOMMENDED]
LoadModule chanserv/main
LoadModule chanserv/access-levels
#LoadModule chanserv/access-xop
#LoadModule chanserv/sendpass
################################################## #########################
# MemoServ modules [RECOMMENDED]
# LoadModule memoserv/main
# LoadModule memoserv/forward
# LoadModule memoserv/ignore
################################################## #########################
# StatServ modules [OPTIONAL]
LoadModule statserv/main
################################################## #########################
# HelpServ module [OPTIONAL]
LoadModule misc/helpserv
################################################## #########################
# HTTP server modules [OPTIONAL]
#LoadModule httpd/main
#LoadModule httpd/auth-ip
#LoadModule httpd/auth-password
#LoadModule httpd/dbaccess
#LoadModule httpd/debug
#LoadModule httpd/redirect
#LoadModule httpd/top-page
################################################## #########################
LoadModule misc/xml-export
LoadModule misc/xml-import
################################################## #########################
# End of example-ircservices.conf