.\" Hal Burgiss <hal@foobox.net> \r
.\" for Junkbuster developers: ijbswa-developers@lists.sourceforge.net\r
.\"\r
-.TH JUNKBUSTER 1 "v2.9.10 (beta) Date: 2001/12/02"\r
+.TH JUNKBUSTER 1 "v2.9.10 (beta) Date: 2002/01/09"\r
\r
.SH NAME\r
\fBjunkbuster\fP\r
\fB\&https:\fP\r
\s-2URL\s0s\r
won't be proxied.\r
+.P\r
+For other browser, check the documentation.\r
\r
.SH CONFIGURATION\r
-All \fBJunkbuster\fP configuration is done via the various configuarion \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
.br\r
\fI/etc/junkbuster/trust\fP\r
.br\r
+\fI/etc/junkbuster/templates/*\fP\r
+.br\r
\fI/var/log/junkbuster/logfile\fP\r
\r
.P\r
and build configuration. More documentation should be included in the local\r
documentation directory, though is not complete at this time.\r
\r
+.SH SIGNALS\r
+\fBJunkbuster\fP use the signal \fISIGHUP\fP (see kill -l) to reload all configuration\r
+files (see CONFIGURATION). This includes the re-open of the logfiles\r
+(logfile and jarfile) eg. used\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 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
+ \r
.SH NOTES\r
This is a development version of \fBJunkbuster\fP. Not all features are \r
complete.\r
http://privacy.net/analyze/\r
.br\r
http://www.squid-cache.org/\r
+.br\r
+http://linuxalpha.ch/packages/\r
\r
.SH DEVELOPMENT TEAM\r
.br\r