2 .\" $Id: ngircd.conf.5,v 1.14 2005/02/14 00:42:41 alex Exp $
4 .TH ngircd.conf 5 "February 2005" ngircd "ngIRCd Manual"
6 ngircd.conf \- configuration file of ngIRCd
8 .B /usr/local/etc/ngircd.conf
11 is the configuration file for
13 which you should adept to your local preferences and needs.
15 The file consists of sections and parameters. A section begins with the name
16 of the section in square brackets and continues until the next section
19 Sections contain parameters of the form
27 Any line beginning with a semicolon (';') or a hash ('#') character is
28 treated as a comment and ignored.
30 The file format is line-based - that means, each newline-terminated line
31 represents either a comment, a section name or a parameter.
33 Section and parameter names are not case sensitive.
34 .SH "SECTION OVERVIEW"
35 The file is separated in four blocks: [Global], [Operator], [Server],
40 section, there is the main configuration like the server name and the
41 ports, on which the server should be listening. IRC operators of this
46 is the section where server links are configured. And
48 blocks are used to configure pre-defined ("persistent") IRC channels.
52 section is used to define the server main configuration, like the server
53 name and the ports on which the server should be listening.
56 Server name in the IRC network
59 Info text of the server. This will be shown by WHOIS and LINKS requests for
62 \fBAdminInfo1\fR, \fBAdminInfo2\fR, \fBAdminEMail\fR
63 Information about the server and the administrator, used by the ADMIN
67 Ports on which the server should listen. There may be more than one port,
68 separated with ','. Default: 6667.
71 The ip address on which the server should listen. Default is empty, so
72 the server listens on all configured ip addresses and interfaces.
75 Text file with the "message of the day" (MOTD). This message will be shown
76 to all users connecting to the server.
79 A simple Phrase (<256 chars) if you don't want to use a motd file.
80 If it is set no MotdFile will be read at all.
83 User ID under which the server should run; you can use the name of the user
89 For this to work the server must have been
90 started with root privileges! In addition, the configuration and MOTD files
91 must be readable by this user, otherwise RESTART and REHASH won't work!
95 Group ID under which the ngIRCd should run; you can use the name of the
96 group or the numerical ID.
101 For this to work the server must have
102 been started with root privileges!
106 A directory to chroot in when everything is initialized. It doesn't need
107 to be populated if ngIRCd is compiled as a static binary. By default ngIRCd
108 won't use the chroot() feature.
113 For this to work the server must have
114 been started with root privileges!
118 This tells ngIRCd to write its current process ID to a file. Note that the
119 pidfile is written AFTER chroot and switching the user ID, i. e. the
120 directory the pidfile resides in must be writeable by the ngIRCd user and
121 exist in the chroot directory (if configured, see above).
125 After <PingTimeout> seconds of inactivity the server will send a PING to
126 the peer to test whether it is alive or not. Default: 120.
129 If a client fails to answer a PING with a PONG within <PongTimeout>
130 seconds, it will be disconnected by the server. Default: 20.
133 The server tries every <ConnectRetry> seconds to establish a link to not yet
134 (or no longer) connected servers. Default: 60.
137 Should IRC Operators be allowed to use the MODE command even if they are
138 not(!) channel-operators? Default: no.
141 Maximum number of simultaneous connection the server is allowed to accept
142 (<=0: unlimited). Default: -1.
144 \fBMaxConnectionsIP\fR
145 Maximum number of simultaneous connections from a single IP address that
146 the server will accept (<=0: unlimited). This configuration options lowers
147 the risk of denial of service attacks (DoS). Default: 5.
150 Maximum number of channels a user can be member of (<=0: no limit).
154 sections are used to define IRC Operators. There may be more than one
156 block, one for each local operator.
159 ID of the operator (may be different of the nick name).
162 Password of the IRC operator.
164 Other servers are configured in
166 sections. If you configure a port for the connection, then this ngIRCd
167 tries to connect to to the other server on the given port; if not, it waits
168 for the other server to connect.
170 The ngIRCd allows "server groups": You can assign an "ID" to every server
171 with which you want this ngIRCd to link. If a server of a group won't
172 answer, the ngIRCd tries to connect to the next server in the given group.
173 But ngIRCd never tries to connect to two servers with the same group ID.
175 There may be more than one
180 IRC name of the server
183 Internet host name of the peer
186 Port of the server to which the ngIRCd should connect. If you assign no port
187 the ngIRCd waits for incoming connections.
190 Own password for this connection. This password has to be configured as
191 "PeerPassword" on the other server.
194 Foreign password for this connection. This password has to be configured as
195 "MyPassword" on the other server.
198 Group of this server (optional).
200 Pre-defined channels can be configured in
202 sections. Such channels are created by the server when starting up and even
203 persist when there are no more members left.
205 Persistent channels are marked with the mode 'P', which can be set and unset
206 by IRC operators like other modes on the fly.
208 There may be more than one
216 Topic for this channel
219 Initial channel modes.
221 It's wise to use "ngircd --configtest" to validate the configuration file
222 after changing it. See
227 .UR mailto:alex@barton.de
232 .UR http://arthur.ath.cx/~alex/ngircd/
233 http://arthur.ath.cx/~alex/ngircd/