7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.1 User Manual"
11 HREF="index.html"><LINK
14 HREF="introduction.html"><LINK
16 TITLE="Note to Upgraders"
17 HREF="upgradersnote.html"><LINK
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy 3.0.1 User Manual</TH
48 HREF="introduction.html"
62 HREF="upgradersnote.html"
83 > is available both in convenient pre-compiled
84 packages for a wide range of operating systems, and as raw source code.
85 For most users, we recommend using the packages, which can be downloaded from our
87 HREF="http://sourceforge.net/projects/ijbswa/"
93 > Note: If you have a previous <SPAN
100 > installation on your system, you
101 will need to remove it. On some platforms, this may be done for you as part
102 of their installation procedure. (See below for your platform). In any case
107 >be sure to backup your old configuration if it is valuable to
111 HREF="upgradersnote.html"
120 NAME="INSTALLATION-PACKAGES"
122 >2.1. Binary Packages</H2
124 >How to install the binary packages depends on your operating system:</P
130 NAME="INSTALLATION-PACK-RPM"
132 >2.1.1. Red Hat, SuSE and Conectiva RPMs</H3
134 > RPMs can be installed with <TT
136 >rpm -Uvh privoxy-3.0.1-1.rpm</TT
142 of configuration files.</P
144 > Note that on Red Hat, <SPAN
154 > be automatically started on system boot. You will
155 need to enable that using <B
162 >, or similar methods. Note that SuSE will
163 automatically start Privoxy in the boot process.</P
165 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
168 >rpm --rebuild privoxy-3.0.1-1.src.rpm</TT
170 will use your locally installed libraries and RPM version. </P
172 > Also note that if you have a <SPAN
176 on your system, you need to remove it first, because the packages conflict.
177 Otherwise, RPM will try to remove <SPAN
181 automatically, before installing <SPAN
191 NAME="INSTALLATION-DEB"
195 > DEBs can be installed with <TT
198 privoxy_3.0.1-1.deb</TT
203 > for the location of configuration
211 NAME="INSTALLATION-PACK-WIN"
215 > Just double-click the installer, which will guide you through
216 the installation process. You will find the configuration files
217 in the same directory as you installed Privoxy in. We do not
218 use the registry of Windows. </P
225 NAME="INSTALLATION-PACK-BINTGZ"
227 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
229 > Create a new directory, <TT
232 > to it, then unzip and
233 untar the archive. For the most part, you'll have to figure out where
241 NAME="INSTALLATION-OS2"
245 > First, make sure that no previous installations of
254 system. Check that no <SPAN
262 your startup folder. </P
264 > Then, just double-click the WarpIN self-installing archive, which will
265 guide you through the installation process. A shadow of the
269 > executable will be placed in your
270 startup folder so it will start automatically whenever OS/2 starts.</P
272 > The directory you choose to install <SPAN
276 into will contain all of the configuration files.</P
283 NAME="INSTALLATION-MAC"
287 > Unzip the downloaded file (you can either double-click on the file
288 from the finder, or from the desktop if you downloaded it there).
289 Then, double-click on the package installer icon named
294 and follow the installation process.
298 > will be installed in the folder
301 >/Library/Privoxy</TT
303 It will start automatically whenever you start up. To prevent it from
304 starting automatically, remove or rename the folder
307 >/Library/StartupItems/Privoxy</TT
310 > To start Privoxy by hand, double-click on
313 >StartPrivoxy.command</TT
317 >/Library/Privoxy</TT
319 Or, type this command in the Terminal:</P
329 > /Library/Privoxy/StartPrivoxy.command
336 > You will be prompted for the administrator password.</P
343 NAME="INSTALLATION-AMIGA"
347 > Copy and then unpack the <TT
350 > archive to a suitable location.
351 All necessary files will be installed into <SPAN
355 directory, including all configuration and log files. To uninstall, just
356 remove this directory.</P
363 NAME="INSTALLATTION-GENTOO"
367 > Gentoo source packages (Ebuilds) for <SPAN
371 contained in the Gentoo Portage Tree (they are not on the download page,
372 but there is a Gentoo section, where you can see when a new
376 > Version is added to the Portage Tree).</P
378 > Before installing <SPAN
381 > under Gentoo just do
385 > to get the latest changes from the
386 Portage tree. With <TT
389 > you install the latest
392 > Configuration files are in <TT
396 documentation is in <TT
398 >/usr/share/doc/privoxy-3.0.1</TT
400 and the Log directory is in <TT
402 >/var/log/privoxy</TT
411 NAME="INSTALLATION-SOURCE"
413 >2.2. Building from Source</H2
415 > The most convenient way to obtain the <SPAN
419 is to download the source tarball from our <A
420 HREF="http://sf.net/projects/ijbswa/"
426 > If you like to live on the bleeding edge and are not afraid of using
427 possibly unstable development versions, you can check out the up-to-the-minute
428 version directly from <A
429 HREF="http://sourceforge.net/cvs/?group_id=11118"
433 > or simply download <A
434 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
445 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
450 HREF="http://www.gnu.org/software/make/make.html"
454 >, and, of course, a C compiler like <A
455 HREF="http://www.gnu.org/software/gcc/gcc.html"
460 > When building from a source tarball (either release version or
462 HREF="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz"
466 >), first unpack the source: </P
476 > tar xzvf privoxy-3.0.1-src* [.tgz or .tar.gz]
477 cd privoxy-3.0.1</PRE
483 > For retrieving the current CVS sources, you'll need CVS installed.
484 Note that sources from CVS are development quality, and may not be
485 stable, or well tested. To download CVS source:</P
495 > cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
496 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
503 > This will create a directory named <TT
507 contain the source tree.</P
509 > You can also check out any <SPAN
516 >, just exchange the <SPAN
520 name with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs
523 > It is also strongly recommended to not run <SPAN
527 as root, and instead it is suggested to create a <SPAN
531 and group for this purpose. See your local documentation for the correct
532 command line to do this.</P
537 > might then look like:</P
547 > privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell</PRE
566 > privoxy:*:7777:</PRE
572 > Some binary packages may do this for you.</P
574 > Then, to build from either unpacked tarball or CVS source:</P
586 ./configure # (--help to see options)
587 make # (the make from gnu, gmake for *BSD)
589 make -n install # (to see where all the files will go)
590 make -s install # (to really install, -s to silence output)</PRE
599 >, you can have the first four steps
600 automatically done for you by just typing:</P
616 > in the freshly downloaded or unpacked source directory.</P
624 > If installing as root, the install will fail
625 unless another user is specified. <B
636 for setting user and group ownership of the configuration files (which need
637 to be writable by the daemon). The specified <SPAN
644 >. Or if there is already a privoxy user on the system, and no
645 user was specified during configure, <B
649 will use the privoxy user. When starting <SPAN
653 it should be run as this same user that owns the configuration and log
656 > Alternately, you can specify <TT
666 > command line, but be sure both already exist:</P
676 > make -s install USER=privoxy GROUP=privoxy</PRE
685 > is specified, the install will assume a group
686 exists with the same name as the specified <TT
691 > The default installation path for <B
698 >. This may of course be customized with
702 > path options. If you are doing
703 a root install to anywhere else besides <TT
707 sure to set the appropriate paths with the correct configure options
710 >./configure --help</B
713 > If you do install to <TT
716 >, the install will use
719 >sysconfdir=$prefix/etc/privoxy</TT
720 > by default. All other
721 destinations, and the direct usage of <TT
725 behave like normal, i.e. will not add the extra <TT
729 directory. This is for a safer install, as there may already exist another
730 program that uses a file with the <SPAN
733 > name, and thus makes
739 > If installing to <TT
742 >, the docs will go by default
745 >$prefix/share/doc</TT
746 >. But if this directory doesn't
747 exist, it will then try <TT
750 > and install there before
753 >$prefix/share/doc</TT
760 > Again, if the installs goes to <TT
778 the logs will go to <TT
780 >/var/log/privoxy/</TT
782 will be created in <TT
784 >/var/run/privoxy.pid</TT
790 > will attempt to set the correct values
794 > (main configuration file). You may want
795 to check this to make sure all values are correct. If appropriate,
796 an init script will be installed, but it is up to the user to determine
797 how and where to start <SPAN
801 script should be checked for correct paths and values, if anything other than
802 a default install is done.</P
804 > If install finds previous versions of any configuration files, these will not
805 be overwritten, and the new ones will be installed with a <SPAN
809 extension. You will then need to manually update the installed configuration
810 files as needed. All template files will be overwritten. If you have
811 customized, local templates, you should save these first. If a previous
815 > is already running, you will
816 have to restart it manually.</P
818 > For more detailed instructions on how to build Redhat and SuSE RPMs,
819 Windows self-extracting installers, building on platforms with
820 special requirements etc, please consult the <A
821 HREF="../developer-manual/newrelease.html"
831 NAME="INSTALLATION-KEEPUPDATED"
833 >2.3. Keeping your Installation Up-to-Date</H2
835 > As user feedback comes in and development continues, we will make updated versions
837 HREF="actions-file.html"
840 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
844 >) and the software itself (including the actions file) available for
847 > If you wish to receive an email notification whenever we release updates of
851 > or the actions file, <A
852 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
855 to our announce mailing list</A
856 >, ijbswa-announce@lists.sourceforge.net.</P
858 > In order not to loose your personal changes and adjustments when updating
873 customization of <SPAN
877 HREF="actions-file.html"
878 >Chapter on actions files</A
887 SUMMARY="Footer navigation table"
898 HREF="introduction.html"
916 HREF="upgradersnote.html"
936 >Note to Upgraders</TD