7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.5 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.5 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.5-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.5-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.5</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 <A
503 HREF="http://sf.net/projects/ijbswa/"
509 > If you like to live on the bleeding edge and are not afraid of using
510 possibly unstable development versions, you can check out the up-to-the-minute
511 version directly from <A
512 HREF="http://sourceforge.net/cvs/?group_id=11118"
523 HREF="http://www.gnu.org/software/autoconf/autoconf.html"
528 HREF="http://www.gnu.org/software/make/make.html"
532 >, and, of course, a C compiler like <A
533 HREF="http://www.gnu.org/software/gcc/gcc.html"
538 > When building from a source tarball,
539 first unpack the source: </P
549 > tar xzvf privoxy-3.0.5-beta-src* [.tgz or .tar.gz]
550 cd privoxy-3.0.5-beta</PRE
556 > For retrieving the current CVS sources, you'll need CVS installed.
557 Note that sources from CVS are development quality, and may not be
558 stable, or well tested. To download CVS source, check the Sourceforge
559 documentation, which might give commands like:</P
569 > cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login
570 cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current
577 > This will create a directory named <TT
581 contain the source tree.</P
583 > You can also check out any <SPAN
590 >, just exchange the <SPAN
594 name with the wanted branch name (Example: v_3_0_branch for the 3.0 cvs
597 > It is also strongly recommended to not run <SPAN
601 as root, and instead it is suggested to create a <SPAN
605 and group for this purpose. See your local documentation for the correct
606 command line to do this. </P
611 > might then look like:</P
621 > privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell</PRE
640 > privoxy:*:7777:</PRE
646 > Some binary packages may do this for you.</P
648 > Then, to build from either unpacked tarball or CVS source:</P
660 ./configure # (--help to see options)
661 make # (the make from GNU, sometimes called gmake)
663 make -n install # (to see where all the files will go)
664 make -s install # (to really install, -s to silence output)</PRE
673 >, you can have the first four steps
674 automatically done for you by just typing:</P
690 > in the freshly downloaded or unpacked source directory.</P
698 > If installing as root, the install will fail
699 unless a non-root user or group is specified, or a <TT
703 user and group already exist on the system. If a non-root user is specified,
704 and no group, then the installation will try to also use a group of the same name
708 >. If a group is specified (and no user), then the
709 support files will be installed as writable by that group, and owned by the
710 user running the installation.</P
722 > options for setting user and group ownership
723 of the configuration files (which need to be writable by the daemon). The
728 >user must already exist</I
734 >, it should be run as this same user to
735 insure write access to configuration and log files.</P
737 > Alternately, you can specify <TT
747 > command line, but be sure both already exist:</P
757 > make -s install USER=privoxy GROUP=privoxy</PRE
763 > The default installation path for <B
770 >. This may of course be customized with
774 > path options. If you are doing
775 a root install to anywhere else besides <TT
779 sure to set the appropriate paths with the correct configure options
782 >./configure --help</B
785 > If you do install to <TT
788 >, the install will use
791 >sysconfdir=$prefix/etc/privoxy</TT
792 > by default. All other
793 destinations, and the direct usage of <TT
797 behave like normal, i.e. will not add the extra <TT
801 directory. This is for a safer install, as there may already exist another
802 program that uses a file with the <SPAN
805 > name, and thus makes
811 > If installing to <TT
814 >, the docs will go by default
817 >$prefix/share/doc</TT
818 >. But if this directory doesn't
819 exist, it will then try <TT
822 > and install there before
825 >$prefix/share/doc</TT
832 > Again, if the installs goes to <TT
850 the logs will go to <TT
852 >/var/log/privoxy/</TT
854 will be created in <TT
856 >/var/run/privoxy.pid</TT
862 > will attempt to set the correct values
866 > (main configuration file). You may want
867 to check this to make sure all values are correct. If appropriate,
868 an init script will be installed, but it is up to the user to determine
869 how and where to start <SPAN
873 script should be checked for correct paths and values, if anything other than
874 a default install is done.</P
876 > If install finds previous versions of any configuration files, these will not
877 be overwritten, and the new ones will be installed with a <SPAN
881 extension. You will then need to manually update the installed configuration
882 files as needed. All template files will be overwritten. If you have
883 customized, local templates, you should save these first. If a previous
887 > is already running, you will
888 have to restart it manually.</P
890 > For more detailed instructions on how to build Redhat and SuSE RPMs,
891 Windows self-extracting installers, building on platforms with
892 special requirements etc, please consult the <A
893 HREF="../developer-manual/newrelease.html"
903 NAME="INSTALLATION-KEEPUPDATED"
905 >2.3. Keeping your Installation Up-to-Date</H2
907 > As user feedback comes in and development continues, we will make updated versions
909 HREF="actions-file.html"
912 HREF="http://sourceforge.net/project/showfiles.php?group_id=11118&release_id=103670"
916 >) and the software itself (including the actions file) available for
919 > If you wish to receive an email notification whenever we release updates of
923 > or the actions file, <A
924 HREF="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/"
927 to our announce mailing list</A
928 >, ijbswa-announce@lists.sourceforge.net.</P
930 > In order not to lose your personal changes and adjustments when updating
949 customizations of <SPAN
953 HREF="actions-file.html"
954 >Chapter on actions files</A
963 SUMMARY="Footer navigation table"
974 HREF="introduction.html"
1012 >What's New in this Release</TD