From 8d8b133bdf3aa0d0bcb8b193d89f875beceaaf6b Mon Sep 17 00:00:00 2001 From: Alexander Barton Date: Mon, 14 Feb 2005 00:42:41 +0000 Subject: [PATCH] Added description for "PidFile", fixed description of "Ports". --- man/ngircd.conf.5 | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/man/ngircd.conf.5 b/man/ngircd.conf.5 index 97d77c6d..49efafde 100644 --- a/man/ngircd.conf.5 +++ b/man/ngircd.conf.5 @@ -1,7 +1,7 @@ .\" -.\" $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 @@ -65,7 +65,7 @@ command. .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 @@ -114,6 +114,13 @@ For this to work the server must have 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 seconds of inactivity the server will send a PING to the peer to test whether it is alive or not. Default: 120. -- 2.39.2