The file consists of sections and parameters. A section begins with the name
of the section in square brackets and continues until the next section
begins.
The file consists of sections and parameters. A section begins with the name
of the section in square brackets and continues until the next section
begins.
Any line beginning with a semicolon (';') or a hash ('#') character is
treated as a comment and ignored.
Any line beginning with a semicolon (';') or a hash ('#') character is
treated as a comment and ignored.
The file format is line-based - that means, each newline-terminated line
represents either a comment, a section name or a parameter.
The file format is line-based - that means, each newline-terminated line
represents either a comment, a section name or a parameter.
The file is separated in four blocks: [Global], [Operator], [Server],
and [Channel].
The file is separated in four blocks: [Global], [Operator], [Server],
and [Channel].
.I [Global]
section is used to define the server main configuration, like the server
name and the ports on which the server should be listening.
.I [Global]
section is used to define the server main configuration, like the server
name and the ports on which the server should be listening.
Ports on which the server should listen. There may be more than one port,
separated with ';'. Default: 6667.
Ports on which the server should listen. There may be more than one port,
separated with ';'. Default: 6667.
Text file with the "message of the day" (MOTD). This message will be shown
to all users connecting to the server.
Text file with the "message of the day" (MOTD). This message will be shown
to all users connecting to the server.
For this to work the server must have been
started with root privileges! In addition, the configuration and MOTD files
must be readable by this user, otherwise RESTART and REHASH won't work!
For this to work the server must have been
started with root privileges! In addition, the configuration and MOTD files
must be readable by this user, otherwise RESTART and REHASH won't work!
After <PingTimeout> seconds of inactivity the server will send a PING to
the peer to test whether it is alive or not. Default: 120.
After <PingTimeout> seconds of inactivity the server will send a PING to
the peer to test whether it is alive or not. Default: 120.
If a client fails to answer a PING with a PONG within <PongTimeout>
seconds, it will be disconnected by the server. Default: 20.
If a client fails to answer a PING with a PONG within <PongTimeout>
seconds, it will be disconnected by the server. Default: 20.
The server tries every <ConnectRetry> seconds to establish a link to not yet
(or no longer) connected servers. Default: 60.
The server tries every <ConnectRetry> seconds to establish a link to not yet
(or no longer) connected servers. Default: 60.
Should IRC Operators be allowed to use the MODE command even if they are
not(!) channel-operators? Default: no.
Should IRC Operators be allowed to use the MODE command even if they are
not(!) channel-operators? Default: no.
Maximum number of simultaneous connection the server is allowed to accept
(<=0: unlimited). Default: -1.
Maximum number of simultaneous connection the server is allowed to accept
(<=0: unlimited). Default: -1.
sections are used to define IRC Operators. There may be more than one
.I [Operator]
block, one for each local operator.
sections are used to define IRC Operators. There may be more than one
.I [Operator]
block, one for each local operator.
-sections. If you configure a port for the connection, then this ngircd
-tries to connect to to the other server on the given port; if not it waits
+sections. If you configure a port for the connection, then this ngIRCd
+tries to connect to to the other server on the given port; if not, it waits
The ngIRCd allows "server groups": You can assign an "ID" to every server
with which you want this ngIRCd to link. If a server of a group won't
answer, the ngIRCd tries to connect to the next server in the given group.
The ngIRCd allows "server groups": You can assign an "ID" to every server
with which you want this ngIRCd to link. If a server of a group won't
answer, the ngIRCd tries to connect to the next server in the given group.
-But the ngircd never tries to connect to two servers with the same group ID.
-
-There may be more than one server block.
-.IP Name
+But ngIRCd never tries to connect to two servers with the same group ID.
+.PP
+There may be more than one
+.I [Server]
+block.
+.TP
+\fBName\fR
Port of the server to which the ngIRCd should connect. If you assign no port
the ngIRCd waits for incoming connections.
Port of the server to which the ngIRCd should connect. If you assign no port
the ngIRCd waits for incoming connections.
Own password for this connection. This password has to be configured as
"PeerPassword" on the other server.
Own password for this connection. This password has to be configured as
"PeerPassword" on the other server.
Foreign password for this connection. This password has to be configured as
"MyPassword" on the other server.
Foreign password for this connection. This password has to be configured as
"MyPassword" on the other server.
-.SH [Channel]
-Pre-defined channels can be configured in [Channel] sections. Such channels
-are created by the server when starting up and even persist when there are
-no more members left.
-
+.SH [CHANNEL]
+Pre-defined channels can be configured in
+.I [Channel]
+sections. Such channels are created by the server when starting up and even
+persist when there are no more members left.
+.PP
Persistent channels are marked with the mode 'P', which can be set and unset
by IRC operators like other modes on the fly.
Persistent channels are marked with the mode 'P', which can be set and unset
by IRC operators like other modes on the fly.