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
21 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
33 SUMMARY="Header navigation table"
42 >Privoxy 3.0.4 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, SuSE and Conectiva RPMs</H3
127 > RPMs can be installed with <TT
129 >rpm -Uvh privoxy-3.0.4-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. Note that SuSE will
156 automatically start Privoxy in the boot process.</P
158 > If you have problems with failed dependencies, try rebuilding the SRC RPM:
161 >rpm --rebuild privoxy-3.0.4-1.src.rpm</TT
163 will use your locally installed libraries and RPM version. </P
165 > Also note that if you have a <SPAN
169 on your system, you need to remove it first, because the packages conflict.
170 Otherwise, RPM will try to remove <SPAN
174 automatically if found, before installing <SPAN
184 NAME="INSTALLATION-DEB"
188 > DEBs can be installed with <TT
190 >apt-get install privoxy</TT
195 > for the location of
196 configuration files.</P
203 NAME="INSTALLATION-PACK-WIN"
207 > Just double-click the installer, which will guide you through
208 the installation process. You will find the configuration files
209 in the same directory as you installed <SPAN
214 > Version 3.0.4 introduces full <SPAN
218 functionality. On Windows only, the <SPAN
222 program has two new command line arguments to install and uninstall
271 > After invoking <SPAN
278 >, you will need to bring up the
282 > service console to assign the user you
286 > to run under, and whether or not you
287 want it to run whenever the system starts. You can start the
291 > services console with the following
295 > If you do not take the manual step
299 > service settings, it will
300 not start. Note too that you will need to give Privoxy a user account that
301 actually exists, or it will not be permitted to
302 write to its log and configuration files.</P
309 NAME="INSTALLATION-PACK-BINTGZ"
311 >2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
313 > Create a new directory, <TT
316 > to it, then unzip and
317 untar the archive. For the most part, you'll have to figure out where
325 NAME="INSTALLATION-OS2"
329 > First, make sure that no previous installations of
338 system. Check that no <SPAN
346 your startup folder. </P
348 > Then, just double-click the WarpIN self-installing archive, which will
349 guide you through the installation process. A shadow of the
353 > executable will be placed in your
354 startup folder so it will start automatically whenever OS/2 starts.</P
356 > The directory you choose to install <SPAN
360 into will contain all of the configuration files.</P
367 NAME="INSTALLATION-MAC"
371 > Unzip the downloaded file (you can either double-click on the file
372 from the finder, or from the desktop if you downloaded it there).
373 Then, double-click on the package installer icon named
378 and follow the installation process.
382 > will be installed in the folder
385 >/Library/Privoxy</TT
387 It will start automatically whenever you start up. To prevent it from
388 starting automatically, remove or rename the folder
391 >/Library/StartupItems/Privoxy</TT
394 > To start Privoxy by hand, double-click on
397 >StartPrivoxy.command</TT
401 >/Library/Privoxy</TT
403 Or, type this command in the Terminal:</P
413 > /Library/Privoxy/StartPrivoxy.command
420 > You will be prompted for the administrator password.</P
427 NAME="INSTALLATION-AMIGA"
431 > Copy and then unpack the <TT
434 > archive to a suitable location.
435 All necessary files will be installed into <SPAN
439 directory, including all configuration and log files. To uninstall, just
440 remove this directory.</P
447 NAME="INSTALLATTION-GENTOO"
451 > Gentoo source packages (Ebuilds) for <SPAN
455 contained in the Gentoo Portage Tree (they are not on the download page,
456 but there is a Gentoo section, where you can see when a new
460 > Version is added to the Portage Tree).</P
462 > Before installing <SPAN
465 > under Gentoo just do
469 > to get the latest changes from the
470 Portage tree. With <TT
473 > you install the latest
476 > Configuration files are in <TT
480 documentation is in <TT
482 >/usr/share/doc/privoxy-3.0.4</TT
484 and the Log directory is in <TT
486 >/var/log/privoxy</TT
495 NAME="INSTALLATION-SOURCE"
497 >2.2. Building from Source</H2
499 > The most convenient way to obtain the <SPAN
503 is to download the source tarball from our <A
504 HREF="http://sf.net/projects/ijbswa/"
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.4-beta-src* [.tgz or .tar.gz]
551 cd privoxy-3.0.4-beta</PRE
557 > For retrieving the current CVS sources, you'll need CVS installed.
558 Note that sources from CVS are 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, and instead it is suggested to create a <SPAN
606 and group for this purpose. See your local documentation for the correct
607 command line to do this. </P
612 > might then look like:</P
622 > privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell</PRE
641 > privoxy:*:7777:</PRE
647 > Some binary packages may do this for you.</P
649 > Then, to build from either unpacked tarball or CVS source:</P
661 ./configure # (--help to see options)
662 make # (the make from GNU, sometimes called gmake)
664 make -n install # (to see where all the files will go)
665 make -s install # (to really install, -s to silence output)</PRE
674 >, you can have the first four steps
675 automatically done for you by just typing:</P
691 > in the freshly downloaded or unpacked source directory.</P
699 > If installing as root, the install will fail
700 unless a non-root user or group is specified, or a <TT
704 user and group already exist on the system. If a non-root user is specified,
705 and no group, then the installation will try to also use a group of the same name
709 >. If a group is specified (and no user), then the
710 support files will be installed as writable by that group, and owned by the
711 user running the installation.</P
723 > options for setting user and group ownership
724 of the configuration files (which need to be writable by the daemon). The
729 >user must already exist</I
735 >, it should be run as this same user to
736 insure write access to configuration and log files.</P
738 > Alternately, you can specify <TT
748 > command line, but be sure both already exist:</P
758 > make -s install USER=privoxy GROUP=privoxy</PRE
764 > The default installation path for <B
771 >. This may of course be customized with
775 > path options. If you are doing
776 a root install to anywhere else besides <TT
780 sure to set the appropriate paths with the correct configure options
783 >./configure --help</B
786 > If you do install to <TT
789 >, the install will use
792 >sysconfdir=$prefix/etc/privoxy</TT
793 > by default. All other
794 destinations, and the direct usage of <TT
798 behave like normal, i.e. will not add the extra <TT
802 directory. This is for a safer install, as there may already exist another
803 program that uses a file with the <SPAN
806 > name, and thus makes
812 > If installing to <TT
815 >, the docs will go by default
818 >$prefix/share/doc</TT
819 >. But if this directory doesn't
820 exist, it will then try <TT
823 > and install there before
826 >$prefix/share/doc</TT
833 > Again, if the installs goes to <TT
851 the logs will go to <TT
853 >/var/log/privoxy/</TT
855 will be created in <TT
857 >/var/run/privoxy.pid</TT
863 > will attempt to set the correct values
867 > (main configuration file). You may want
868 to check this to make sure all values are correct. If appropriate,
869 an init script will be installed, but it is up to the user to determine
870 how and where to start <SPAN
874 script should be checked for correct paths and values, if anything other than
875 a default install is done.</P
877 > If install finds previous versions of any configuration files, these will not
878 be overwritten, and the new ones will be installed with a <SPAN
882 extension. You will then need to manually update the installed configuration
883 files as needed. All template files will be overwritten. If you have
884 customized, local templates, you should save these first. If a previous
888 > is already running, you will
889 have to restart it manually.</P
891 > For more detailed instructions on how to build Redhat and SuSE RPMs,
892 Windows self-extracting installers, building on platforms with
893 special requirements etc, please consult the <A
894 HREF="../developer-manual/newrelease.html"
904 NAME="INSTALLATION-KEEPUPDATED"
906 >2.3. Keeping your Installation Up-to-Date</H2
908 > As user feedback comes in and development continues, we will make updated versions
910 HREF="actions-file.html"
913 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
917 >) and the software itself (including the actions file) available for
920 > If you wish to receive an email notification whenever we release updates of
924 > or the actions file, <A
925 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
928 to our announce mailing list</A
929 >, ijbswa-announce@lists.sourceforge.net.</P
931 > In order not to lose your personal changes and adjustments when updating
950 customizations of <SPAN
954 HREF="actions-file.html"
955 >Chapter on actions files</A
964 SUMMARY="Footer navigation table"
975 HREF="introduction.html"
1013 >What's New in this Release</TD