X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=junkbuster.1;h=d5847a1979c6e7fc2a9a66ba1c47bdb9d1fd314c;hp=4d6839e535a1c745d76c880b7f193bbcadaf7664;hb=f31652aedd0c6593032a6979a35d4c4151462f09;hpb=f8b22f6b3563d2fa7cffce9d0aa3726cafe9183f diff --git a/junkbuster.1 b/junkbuster.1 index 4d6839e5..d5847a19 100644 --- a/junkbuster.1 +++ b/junkbuster.1 @@ -2,7 +2,7 @@ .\" Hal Burgiss .\" for Junkbuster developers: ijbswa-developers@lists.sourceforge.net .\" -.TH JUNKBUSTER 1 "v2.9.10 (alpha) Date: 2001/12/01" +.TH JUNKBUSTER 1 "v2.9.10 (beta) Date: 2002/01/09" .SH NAME \fBjunkbuster\fP @@ -68,9 +68,11 @@ otherwise \fB\&https:\fP \s-2URL\s0s won't be proxied. +.P +For other browser, check the documentation. .SH CONFIGURATION -All \fBJunkbuster\fP configuration is done via the various configuarion +All \fBJunkbuster\fP configuration is done via the various configuration files. The default configuration files are: \fIconfig\fP, \fIijb.action\fP, and \fIre_filterfile\fP. These are well commented. On Unix and Unix-like systems, these are located in \fI/etc/junkbuster/\fP @@ -125,7 +127,7 @@ A brief example of what an \fIijb.action\fP configuration might look like: # Now set exceptions to the above defined policies ####### -# Sites that DO need persistant cookies +# Sites where we want persistant cookies {-no-cookies -no-cookies-keep} .redhat.com .sun.com @@ -141,6 +143,7 @@ A brief example of what an \fIijb.action\fP configuration might look like: +add-header{X-User-Tracking: No thanks!} -filter} privacy.net +# Block, and treat these URLs as 'images'. {+imageblock} .adforce.imgis.com .ad.preferences.com/image.* @@ -188,8 +191,18 @@ options. .br \fI/etc/junkbuster/ijb.action\fP .br +\fI/etc/junkbuster/ijb-advanced.action\fP +.br +\fI/etc/junkbuster/ijb-basic.action\fP +.br +\fI/etc/junkbuster/ijb-intermediate.action\fP +.br \fI/etc/junkbuster/re_filterfile\fP .br +\fI/etc/junkbuster/trust\fP +.br +\fI/etc/junkbuster/templates/*\fP +.br \fI/var/log/junkbuster/logfile\fP .P @@ -197,6 +210,17 @@ Various other files should be included, but may vary depending on platform and build configuration. More documentation should be included in the local documentation directory, though is not complete at this time. +.SH SIGNALS +\fBJunkbuster\fP use the signal \fISIGHUP\fP (see kill -l) to reload all configuration +files (see CONFIGURATION). This includes the re-open of the logfiles +(logfile and jarfile) eg. used +after rotation of the logfiles by logrotate. +The \fISIGHUP\fP behavior is only for UNIX like OS'. +.br +However the configfile will be re-read if \fBJunkbuster\fP detects a changed +modification time and then behaves like a re-start of \fBJunkbuster\fP +in context of all the pertinent files. + .SH NOTES This is a development version of \fBJunkbuster\fP. Not all features are complete. @@ -220,6 +244,8 @@ http://www.junkbusters.com/ht/en/cookies.html\" cookies.html# http://privacy.net/analyze/ .br http://www.squid-cache.org/ +.br +http://linuxalpha.ch/packages/ .SH DEVELOPMENT TEAM .br