7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.6 User Manual"
11 HREF="index.html"><LINK
14 HREF="introduction.html"><LINK
16 TITLE="What's New in this Release"
17 HREF="whatsnew.html"><LINK
21 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
33 SUMMARY="Header navigation table"
42 >Privoxy 3.0.6 User Manual</TH
50 HREF="introduction.html"
85 > is available both in convenient pre-compiled
86 packages for a wide range of operating systems, and as raw source code.
87 For most users, we recommend using the packages, which can be downloaded from our
89 HREF="http://sourceforge.net/projects/ijbswa/"
96 On some platforms, the installer may remove previously installed versions, if
97 found. (See below for your platform). In any case <SPAN
102 your old configuration if it is valuable to you.</I
105 HREF="whatsnew.html#UPGRADERSNOTE"
106 >note to upgraders</A
113 NAME="INSTALLATION-PACKAGES"
115 >2.1. Binary Packages</H2
117 >How to install the binary packages depends on your operating system:</P
123 NAME="INSTALLATION-PACK-RPM"
125 >2.1.1. Red Hat and Fedora RPMs</H3
127 > RPMs can be installed with <TT
129 >rpm -Uvh privoxy-3.0.6-1.rpm</TT
135 of configuration files.</P
137 > Note that on Red Hat, <SPAN
147 > be automatically started on system boot. You will
148 need to enable that using <B
155 >, or similar methods. </P
157 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
160 >rpm --rebuild privoxy-3.0.6-1.src.rpm</TT
162 will use your locally installed libraries and RPM version. </P
164 > Also note that if you have a <SPAN
168 on your system, you need to remove it first, because the packages conflict.
169 Otherwise, RPM will try to remove <SPAN
173 automatically if found, before installing <SPAN
183 NAME="INSTALLATION-DEB"
187 > DEBs can be installed with <TT
189 >apt-get install privoxy</TT
194 > for the location of
195 configuration files.</P
202 NAME="INSTALLATION-PACK-WIN"
206 > Just double-click the installer, which will guide you through
207 the installation process. You will find the configuration files
208 in the same directory as you installed <SPAN
213 > Version 3.0.4 introduced full <SPAN
217 functionality. On Windows only, the <SPAN
221 program has two new command line arguments to install and uninstall
270 > After invoking <SPAN
277 >, you will need to bring up the
281 > service console to assign the user you
285 > to run under, and whether or not you
286 want it to run whenever the system starts. You can start the
290 > services console with the following
294 >. If you do not take the manual step
298 > service settings, it will
299 not start. Note too that you will need to give Privoxy a user account that
300 actually exists, or it will not be permitted to
301 write to its log and configuration files.</P
308 NAME="INSTALLATION-PACK-BINTGZ"
310 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
312 > Create a new directory, <TT
315 > to it, then unzip and
316 untar the archive. For the most part, you'll have to figure out where
324 NAME="INSTALLATION-OS2"
328 > First, make sure that no previous installations of
337 system. Check that no <SPAN
345 your startup folder. </P
347 > Then, just double-click the WarpIN self-installing archive, which will
348 guide you through the installation process. A shadow of the
352 > executable will be placed in your
353 startup folder so it will start automatically whenever OS/2 starts.</P
355 > The directory you choose to install <SPAN
359 into will contain all of the configuration files.</P
366 NAME="INSTALLATION-MAC"
370 > Unzip the downloaded file (you can either double-click on the file
371 from the finder, or from the desktop if you downloaded it there).
372 Then, double-click on the package installer icon named
377 and follow the installation process.
381 > will be installed in the folder
384 >/Library/Privoxy</TT
386 It will start automatically whenever you start up. To prevent it from
387 starting automatically, remove or rename the folder
390 >/Library/StartupItems/Privoxy</TT
393 > To start Privoxy by hand, double-click on
396 >StartPrivoxy.command</TT
400 >/Library/Privoxy</TT
402 Or, type this command in the Terminal:</P
412 > /Library/Privoxy/StartPrivoxy.command
419 > You will be prompted for the administrator password.</P
426 NAME="INSTALLATION-AMIGA"
430 > Copy and then unpack the <TT
433 > archive to a suitable location.
434 All necessary files will be installed into <SPAN
438 directory, including all configuration and log files. To uninstall, just
439 remove this directory.</P
446 NAME="INSTALLATTION-GENTOO"
450 > Gentoo source packages (Ebuilds) for <SPAN
454 contained in the Gentoo Portage Tree (they are not on the download page,
455 but there is a Gentoo section, where you can see when a new
459 > Version is added to the Portage Tree).</P
461 > Before installing <SPAN
464 > under Gentoo just do
468 > to get the latest changes from the
469 Portage tree. With <TT
472 > you install the latest
475 > Configuration files are in <TT
479 documentation is in <TT
481 >/usr/share/doc/privoxy-3.0.6</TT
483 and the Log directory is in <TT
485 >/var/log/privoxy</TT
494 NAME="INSTALLATION-SOURCE"
496 >2.2. Building from Source</H2
498 > The most convenient way to obtain the <SPAN
502 is to download the source tarball from our
504 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&package_id=10571"
510 > If you like to live on the bleeding edge and are not afraid of using
511 possibly unstable development versions, you can check out the up-to-the-minute
512 version directly from <A
513 HREF="http://sourceforge.net/cvs/?group_id=11118"
524 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
529 HREF="http://www.gnu.org/software/make/make.html"
533 >, and, of course, a C compiler like <A
534 HREF="http://www.gnu.org/software/gcc/gcc.html"
539 > When building from a source tarball,
540 first unpack the source: </P
550 > tar xzvf privoxy-3.0.6-src* [.tgz or .tar.gz]
551 cd privoxy-3.0.6</PRE
557 > For retrieving the current CVS sources, you'll need a CVS client installed.
558 Note that sources from CVS are typically development quality, and may not be
559 stable, or well tested. To download CVS source, check the Sourceforge
560 documentation, which might give commands like:</P
570 > cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login
571 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current
578 > This will create a directory named <TT
582 contain the source tree.</P
584 > You can also check out any <SPAN
591 >, just exchange the <SPAN
595 name with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs
598 > It is also strongly recommended to not run <SPAN
602 as root. You should configure/install/run <SPAN
606 an unprivileged user, preferably by creating a <SPAN
610 and group just for this purpose. See your local documentation for the correct
611 command line to do add new users and groups (something like
615 >, but the command syntax may vary from platform
621 > might then look like:</P
631 > privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell</PRE
650 > privoxy:*:7777:</PRE
656 > Some binary packages may do this for you.</P
658 > Then, to build from either unpacked tarball or CVS source:</P
670 ./configure # (--help to see options)
671 make # (the make from GNU, sometimes called gmake)
672 su # Possibly required
673 make -n install # (to see where all the files will go)
674 make -s install # (to really install, -s to silence output)</PRE
683 >, you can have the first four steps
684 automatically done for you by just typing:</P
700 > in the freshly downloaded or unpacked source directory.</P
702 > To build an executable with security enhanced features so that
703 users cannot easily bypass the proxy (e.g. <SPAN
705 >"Go There Anyway"</SPAN
707 alter their own configurations, <B
720 > ./configure --disable-toggle --disable-editor --disable-force</PRE
726 >Then build as above.</P
734 > If installing as root, the install will fail
735 unless a non-root user or group is specified, or a <TT
739 user and group already exist on the system. If a non-root user is specified,
740 and no group, then the installation will try to also use a group of the same name
744 >. If a group is specified (and no user), then the
745 support files will be installed as writable by that group, and owned by the
746 user running the installation.</P
758 > options for setting user and group ownership
759 of the configuration files (which need to be writable by the daemon). The
764 >user must already exist</I
770 >, it must be run as this same user to
771 insure write access to configuration and log files!</P
773 > Alternately, you can specify <TT
783 > command line, but be sure both already exist:</P
793 > make -s install USER=privoxy GROUP=privoxy</PRE
799 > The default installation path for <B
806 >. This may of course be customized with
810 > path options. If you are doing
811 an install to anywhere besides <TT
815 sure to set the appropriate paths with the correct configure options
818 >./configure --help</B
819 >). Non-privileged users must of course
820 have write access permissions to wherever the target installation is going.</P
822 > If you do install to <TT
825 >, the install will use
828 >sysconfdir=$prefix/etc/privoxy</TT
829 > by default. All other
830 destinations, and the direct usage of <TT
834 behave like normal, i.e. will not add the extra <TT
838 directory. This is for a safer install, as there may already exist another
839 program that uses a file with the <SPAN
842 > name, and thus makes
848 > If installing to <TT
851 >, the documentation will go
854 >$prefix/share/doc</TT
855 >. But if this directory
856 doesn't exist, it will then try <TT
860 there before creating a new <TT
862 >$prefix/share/doc</TT
869 > Again, if the installs goes to <TT
887 the logs will go to <TT
889 >/var/log/privoxy/</TT
891 will be created in <TT
893 >/var/run/privoxy.pid</TT
899 > will attempt to set the correct values
903 > (main configuration file). You should
904 check this to make sure all values are correct. If appropriate,
905 an init script will be installed, but it is up to the user to determine
906 how and where to start <SPAN
910 script should be checked for correct paths and values, if anything other than
911 a default install is done.</P
913 > If install finds previous versions of local configuration files, most of
914 these will not be overwritten, and the new ones will be installed with a
918 > extension. default.action, default.filter, and
919 standard.action <SPAN
923 >will be overwritten</I
925 >. You will then need
926 to manually update the other installed configuration files as needed. All
927 template files will be overwritten. If you have customized, local templates,
928 you should save these first, and in fact it is wise to always save any
929 important configuration files <SPAN
931 >"just in case"</SPAN
936 > is already running, you will
937 have to restart it manually.</P
939 > For more detailed instructions on how to build Redhat RPMs,
940 Windows self-extracting installers, building on platforms with
941 special requirements etc, please consult the <A
942 HREF="../developer-manual/newrelease.html"
952 NAME="INSTALLATION-KEEPUPDATED"
954 >2.3. Keeping your Installation Up-to-Date</H2
956 > As user feedback comes in and development continues, we will make updated versions
958 HREF="actions-file.html"
961 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
965 >) and the software itself (including the actions file) available for
968 > If you wish to receive an email notification whenever we release updates of
972 > or the actions file, <A
973 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
976 to our announce mailing list</A
977 >, ijbswa-announce@lists.sourceforge.net.</P
979 > In order not to lose your personal changes and adjustments when updating
998 customizations of <SPAN
1002 HREF="actions-file.html"
1003 >Chapter on actions files</A
1012 SUMMARY="Footer navigation table"
1023 HREF="introduction.html"
1041 HREF="whatsnew.html"
1061 >What's New in this Release</TD