2 .\" $Id: ngircd.conf.5.tmpl,v 1.7 2007/11/23 16:26:03 fw Exp $
4 .TH ngircd.conf 5 "August 2005" ngircd "ngIRCd Manual"
6 ngircd.conf \- configuration file of ngIRCd
8 .B :ETCDIR:/ngircd.conf
11 is the configuration file of the
13 Internet Relay Chat (IRC) daemon which you should adept to your local
14 preferences and needs.
16 The file consists of sections and parameters. A section begins with the name
17 of the section in square brackets and continues until the next section
20 Sections contain parameters of the form
28 Empty lines and any line beginning with a semicolon (';') or a hash ('#')
29 character is treated as a comment and will be ignored.
31 The file format is line-based - that means, each newline-terminated line
32 represents either a comment, a section name or a parameter.
34 Section and parameter names are not case sensitive.
35 .SH "SECTION OVERVIEW"
36 The file can contain blocks of four types: [Global], [Operator], [Server],
41 section, there is the main configuration like the server name and the
42 ports on which the server should be listening. IRC operators of this
47 is the section where server links are configured. And
49 blocks are used to configure pre-defined ("persistent") IRC channels.
51 There can be more than one [Operator], [Server] and [Channel] sections
52 per configuration file, but only one [Global] section.
56 section is used to define the server main configuration, like the server
57 name and the ports on which the server should be listening.
60 Server name in the IRC network
63 Info text of the server. This will be shown by WHOIS and LINKS requests for
66 \fBAdminInfo1\fR, \fBAdminInfo2\fR, \fBAdminEMail\fR
67 Information about the server and the administrator, used by the ADMIN
71 Ports on which the server should listen. There may be more than one port,
72 separated with ','. Default: 6667.
75 The IP address on which the server should listen. Default is empty, so
76 the server listens on all configured IP addresses and interfaces.
79 Text file with the "message of the day" (MOTD). This message will be shown
80 to all users connecting to the server.
83 A simple Phrase (<256 chars) if you don't want to use a MOTD file.
84 If it is set no MotdFile will be read at all.
87 User ID under which the server should run; you can use the name of the user
93 For this to work the server must have been
94 started with root privileges! In addition, the configuration and MOTD files
95 must be readable by this user, otherwise RESTART and REHASH won't work!
99 Group ID under which the ngIRCd should run; you can use the name of the
100 group or the numerical ID.
105 For this to work the server must have
106 been started with root privileges!
110 A directory to chroot in when everything is initialized. It doesn't need
111 to be populated if ngIRCd is compiled as a static binary. By default ngIRCd
112 won't use the chroot() feature.
117 For this to work the server must have
118 been started with root privileges!
122 This tells ngIRCd to write its current process ID to a file. Note that the
123 pidfile is written AFTER chroot and switching the user ID, i. e. the
124 directory the pidfile resides in must be writeable by the ngIRCd user and
125 exist in the chroot directory (if configured, see above).
129 After <PingTimeout> seconds of inactivity the server will send a PING to
130 the peer to test whether it is alive or not. Default: 120.
133 If a client fails to answer a PING with a PONG within <PongTimeout>
134 seconds, it will be disconnected by the server. Default: 20.
137 The server tries every <ConnectRetry> seconds to establish a link to not yet
138 (or no longer) connected servers. Default: 60.
141 Should IRC Operators be allowed to use the MODE command even if they are
142 not(!) channel-operators? Default: no.
145 If OperCanUseMode is enabled, this may lead the compatibility problems with
146 Servers that run the ircd-irc2 Software. This Option "masks" mode requests
147 by non-chanops as if they were coming from the server. Default: no.
149 \fBPredefChannelsOnly\fR
150 If enabled, no new channels can be created. Useful if
151 you do not want to have channels other than those defined in
156 If enabled, ngircd will not make DNS lookups when clients connect.
157 If you configure ngircd to connect to other servers, ngircd may still
158 perform a DNS lookup if required.
162 Set this to no if you do not want ngircd to accept clients using the standard internet protocol, ipv4.
163 This allows use of ngircd in ipv6-only setups.
167 Set this to no if you do not want ngircd to accept clients using the new internet protocol, ipv6.
171 Set this to no if you do not want ngircd to connect to other irc servers using ipv4.
172 This allows use of ngircd in ipv6-only setups.
176 Set this to no if you do not want ngircd to connect to other irc servers using ipv6.
180 Maximum number of simultaneous connection the server is allowed to accept
181 (0: unlimited). Default: 0.
183 \fBMaxConnectionsIP\fR
184 Maximum number of simultaneous connections from a single IP address that
185 the server will accept (0: unlimited). This configuration options lowers
186 the risk of denial of service attacks (DoS). Default: 5.
189 Maximum number of channels a user can be member of (0: no limit).
193 Maximum length of an user nick name (Default: 9, as in RFC 2812). Please
194 note that all servers in an IRC network MUST use the same maximum nick name
198 sections are used to define IRC Operators. There may be more than one
200 block, one for each local operator.
203 ID of the operator (may be different of the nick name).
206 Password of the IRC operator.
209 Mask that is to be checked before an /OPER for this account is accepted.
210 Example: nick!ident@*.example.com
212 Other servers are configured in
214 sections. If you configure a port for the connection, then this ngIRCd
215 tries to connect to to the other server on the given port; if not, it waits
216 for the other server to connect.
218 The ngIRCd allows "server groups": You can assign an "ID" to every server
219 with which you want this ngIRCd to link. If a server of a group won't
220 answer, the ngIRCd tries to connect to the next server in the given group.
221 But ngIRCd never tries to connect to two servers with the same group ID.
223 There may be more than one
228 IRC name of the server
231 Internet host name of the peer
234 IP address to use as source IP for the outgoing connection. Default ist
235 to let the operating system decide.
238 Port of the server to which the ngIRCd should connect. If you assign no port
239 the ngIRCd waits for incoming connections.
242 Own password for this connection. This password has to be configured as
243 "PeerPassword" on the other server. Must not have ':' as first character.
246 Foreign password for this connection. This password has to be configured as
247 "MyPassword" on the other server.
250 Group of this server (optional).
252 Disable automatic connection even if port value is specified. Default: false.
253 You can use the IRC Operator command CONNECT later on to create the link.
255 Pre-defined channels can be configured in
257 sections. Such channels are created by the server when starting up and even
258 persist when there are no more members left.
260 Persistent channels are marked with the mode 'P', which can be set and unset
261 by IRC operators like other modes on the fly.
263 There may be more than one
271 Topic for this channel
274 Initial channel modes.
277 Sets initial channel key (only relevant if mode k is set)
280 Set maximum user limit for this channel (only relevant if mode l is set)
282 It's wise to use "ngircd --configtest" to validate the configuration file
283 after changing it. See
288 .UR mailto:alex@barton.de
293 .UR http://ngircd.barton.de/
294 http://ngircd.barton.de/