commit - ec30cd4e5feb7890ff9e1a0317a6cf06d16a3629
commit + 8d8b133bdf3aa0d0bcb8b193d89f875beceaaf6b
blob - 97d77c6d1b35e8142a08bbcfce34d10a291c95ca
blob + 49efafded42ac06e7c4b3c5eb84c67d4f8419ab5
--- man/ngircd.conf.5
+++ man/ngircd.conf.5
.\"
-.\" $Id: ngircd.conf.5,v 1.13 2004/05/07 11:19:20 alex Exp $
+.\" $Id: ngircd.conf.5,v 1.14 2005/02/14 00:42:41 alex Exp $
.\"
-.TH ngircd.conf 5 "Mai 2003" ngircd "ngIRCd Manual"
+.TH ngircd.conf 5 "February 2005" ngircd "ngIRCd Manual"
.SH NAME
ngircd.conf \- configuration file of ngIRCd
.SH SYNOPSIS
.TP
\fBPorts\fR
Ports on which the server should listen. There may be more than one port,
-separated with ';'. Default: 6667.
+separated with ','. Default: 6667.
.TP
\fBListen\fR
The ip address on which the server should listen. Default is empty, so
been started with root privileges!
.RE
.TP
+\fBPidFile\fR
+This tells ngIRCd to write its current process ID to a file. Note that the
+pidfile is written AFTER chroot and switching the user ID, i. e. the
+directory the pidfile resides in must be writeable by the ngIRCd user and
+exist in the chroot directory (if configured, see above).
+.RE
+.TP
\fBPingTimeout\fR
After <PingTimeout> seconds of inactivity the server will send a PING to
the peer to test whether it is alive or not. Default: 120.