7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.4 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
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy 3.0.4 User Manual</TH
48 HREF="introduction.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="whatsnew.html#UPGRADERSNOTE"
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.4-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.4-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
197 >apt-get install privoxy</TT
202 > for the location of
203 configuration files.</P
210 NAME="INSTALLATION-PACK-WIN"
214 > Just double-click the installer, which will guide you through
215 the installation process. You will find the configuration files
216 in the same directory as you installed Privoxy in. </P
223 NAME="INSTALLATION-PACK-BINTGZ"
225 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
227 > Create a new directory, <TT
230 > to it, then unzip and
231 untar the archive. For the most part, you'll have to figure out where
239 NAME="INSTALLATION-OS2"
243 > First, make sure that no previous installations of
252 system. Check that no <SPAN
260 your startup folder. </P
262 > Then, just double-click the WarpIN self-installing archive, which will
263 guide you through the installation process. A shadow of the
267 > executable will be placed in your
268 startup folder so it will start automatically whenever OS/2 starts.</P
270 > The directory you choose to install <SPAN
274 into will contain all of the configuration files.</P
281 NAME="INSTALLATION-MAC"
285 > Unzip the downloaded file (you can either double-click on the file
286 from the finder, or from the desktop if you downloaded it there).
287 Then, double-click on the package installer icon named
292 and follow the installation process.
296 > will be installed in the folder
299 >/Library/Privoxy</TT
301 It will start automatically whenever you start up. To prevent it from
302 starting automatically, remove or rename the folder
305 >/Library/StartupItems/Privoxy</TT
308 > To start Privoxy by hand, double-click on
311 >StartPrivoxy.command</TT
315 >/Library/Privoxy</TT
317 Or, type this command in the Terminal:</P
327 > /Library/Privoxy/StartPrivoxy.command
334 > You will be prompted for the administrator password.</P
341 NAME="INSTALLATION-AMIGA"
345 > Copy and then unpack the <TT
348 > archive to a suitable location.
349 All necessary files will be installed into <SPAN
353 directory, including all configuration and log files. To uninstall, just
354 remove this directory.</P
361 NAME="INSTALLATTION-GENTOO"
365 > Gentoo source packages (Ebuilds) for <SPAN
369 contained in the Gentoo Portage Tree (they are not on the download page,
370 but there is a Gentoo section, where you can see when a new
374 > Version is added to the Portage Tree).</P
376 > Before installing <SPAN
379 > under Gentoo just do
383 > to get the latest changes from the
384 Portage tree. With <TT
387 > you install the latest
390 > Configuration files are in <TT
394 documentation is in <TT
396 >/usr/share/doc/privoxy-3.0.4</TT
398 and the Log directory is in <TT
400 >/var/log/privoxy</TT
409 NAME="INSTALLATION-SOURCE"
411 >2.2. Building from Source</H2
413 > The most convenient way to obtain the <SPAN
417 is to download the source tarball from our <A
418 HREF="http://sf.net/projects/ijbswa/"
424 > If you like to live on the bleeding edge and are not afraid of using
425 possibly unstable development versions, you can check out the up-to-the-minute
426 version directly from <A
427 HREF="http://sourceforge.net/cvs/?group_id=11118"
438 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
443 HREF="http://www.gnu.org/software/make/make.html"
447 >, and, of course, a C compiler like <A
448 HREF="http://www.gnu.org/software/gcc/gcc.html"
453 > When building from a source tarball,
454 first unpack the source: </P
464 > tar xzvf privoxy-3.0.4-beta-src* [.tgz or .tar.gz]
465 cd privoxy-3.0.4-beta</PRE
471 > For retrieving the current CVS sources, you'll need CVS installed.
472 Note that sources from CVS are development quality, and may not be
473 stable, or well tested. To download CVS source, check the Sourceforge
474 documentation, which might give commands like:</P
484 > cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login
485 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current
492 > This will create a directory named <TT
496 contain the source tree.</P
498 > You can also check out any <SPAN
505 >, just exchange the <SPAN
509 name with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs
512 > It is also strongly recommended to not run <SPAN
516 as root, and instead it is suggested to create a <SPAN
520 and group for this purpose. See your local documentation for the correct
521 command line to do this. </P
526 > might then look like:</P
536 > privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell</PRE
555 > privoxy:*:7777:</PRE
561 > Some binary packages may do this for you.</P
563 > Then, to build from either unpacked tarball or CVS source:</P
575 ./configure # (--help to see options)
576 make # (the make from GNU, sometimes called gmake)
578 make -n install # (to see where all the files will go)
579 make -s install # (to really install, -s to silence output)</PRE
588 >, you can have the first four steps
589 automatically done for you by just typing:</P
605 > in the freshly downloaded or unpacked source directory.</P
613 > If installing as root, the install will fail
614 unless a non-root user or group is specified, or a <TT
618 user and group already exist on the system. If a non-root user is specified,
619 and no group, then the installation will try to also use a group of the same name
623 >. If a group is specified (and no user), then the
624 support files will be installed as writable by that group, and owned by the
625 user running the installation.</P
637 > options for setting user and group ownership
638 of the configuration files (which need to be writable by the daemon). The
643 >user must already exist</I
649 >, it should be run as this same user to
650 insure write access to configuration and log files.</P
652 > Alternately, you can specify <TT
662 > command line, but be sure both already exist:</P
672 > make -s install USER=privoxy GROUP=privoxy</PRE
678 > The default installation path for <B
685 >. This may of course be customized with
689 > path options. If you are doing
690 a root install to anywhere else besides <TT
694 sure to set the appropriate paths with the correct configure options
697 >./configure --help</B
700 > If you do install to <TT
703 >, the install will use
706 >sysconfdir=$prefix/etc/privoxy</TT
707 > by default. All other
708 destinations, and the direct usage of <TT
712 behave like normal, i.e. will not add the extra <TT
716 directory. This is for a safer install, as there may already exist another
717 program that uses a file with the <SPAN
720 > name, and thus makes
726 > If installing to <TT
729 >, the docs will go by default
732 >$prefix/share/doc</TT
733 >. But if this directory doesn't
734 exist, it will then try <TT
737 > and install there before
740 >$prefix/share/doc</TT
747 > Again, if the installs goes to <TT
765 the logs will go to <TT
767 >/var/log/privoxy/</TT
769 will be created in <TT
771 >/var/run/privoxy.pid</TT
777 > will attempt to set the correct values
781 > (main configuration file). You may want
782 to check this to make sure all values are correct. If appropriate,
783 an init script will be installed, but it is up to the user to determine
784 how and where to start <SPAN
788 script should be checked for correct paths and values, if anything other than
789 a default install is done.</P
791 > If install finds previous versions of any configuration files, these will not
792 be overwritten, and the new ones will be installed with a <SPAN
796 extension. You will then need to manually update the installed configuration
797 files as needed. All template files will be overwritten. If you have
798 customized, local templates, you should save these first. If a previous
802 > is already running, you will
803 have to restart it manually.</P
805 > For more detailed instructions on how to build Redhat and SuSE RPMs,
806 Windows self-extracting installers, building on platforms with
807 special requirements etc, please consult the <A
808 HREF="../developer-manual/newrelease.html"
818 NAME="INSTALLATION-KEEPUPDATED"
820 >2.3. Keeping your Installation Up-to-Date</H2
822 > As user feedback comes in and development continues, we will make updated versions
824 HREF="actions-file.html"
827 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
831 >) and the software itself (including the actions file) available for
834 > If you wish to receive an email notification whenever we release updates of
838 > or the actions file, <A
839 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
842 to our announce mailing list</A
843 >, ijbswa-announce@lists.sourceforge.net.</P
845 > In order not to lose your personal changes and adjustments when updating
864 customizations of <SPAN
868 HREF="actions-file.html"
869 >Chapter on actions files</A
878 SUMMARY="Footer navigation table"
889 HREF="introduction.html"
927 >What's New in this Release</TD