.\" Hal Burgiss <hal@foobox.net> \r
.\" for Junkbuster developers: ijbswa-developers@lists.sourceforge.net\r
.\"\r
.\" Hal Burgiss <hal@foobox.net> \r
.\" for Junkbuster developers: ijbswa-developers@lists.sourceforge.net\r
.\"\r
.P\r
If the configuration file is not specified on the command line,\r
\fBJunkbuster\fP will look for a file named \fIconfig\fP in the \r
.P\r
If the configuration file is not specified on the command line,\r
\fBJunkbuster\fP will look for a file named \fIconfig\fP in the \r
\r
.SH CONFIGURATION\r
All \fBJunkbuster\fP configuration is done via the various configuration \r
files. The default configuration files are: \fIconfig\fP, \r
\fIijb.action\fP, and \fIre_filterfile\fP. These are well commented. \r
On Unix and Unix-like systems, these are located in \fI/etc/junkbuster/\fP \r
\r
.SH CONFIGURATION\r
All \fBJunkbuster\fP configuration is done via the various configuration \r
files. The default configuration files are: \fIconfig\fP, \r
\fIijb.action\fP, and \fIre_filterfile\fP. These are well commented. \r
On Unix and Unix-like systems, these are located in \fI/etc/junkbuster/\fP \r
as the \fBJunkbuster\fP executable. \r
.P\r
The name and number of configuration files has changed from previous versions,\r
as the \fBJunkbuster\fP executable. \r
.P\r
The name and number of configuration files has changed from previous versions,\r
after rotation of the logfiles by logrotate.\r
The \fISIGHUP\fP behavior is only for UNIX like OS'.\r
.br\r
after rotation of the logfiles by logrotate.\r
The \fISIGHUP\fP behavior is only for UNIX like OS'.\r
.br\r
-However the configfile will be read if \fBJunkbuster\fP notice a different\r
-modification time of this file and behaves so like start of \fBJunkbuster\fP \r
-in context of all the files.\r
+However the configfile will be re-read if \fBJunkbuster\fP detects a changed\r
+modification time and then behaves like a re-start of \fBJunkbuster\fP \r
+in context of all the pertinent files.\r