Note: If you have a previous Junkbuster or - Privoxy installation on your system, you - will need to remove it. On some platforms, this may be done for you as part - of their installation procedure. (See below for your platform). In any case - Note: + On some platforms, the installer may remove previously installed versions, if + found. (See below for your platform). In any case be sure to backup your old configuration if it is valuable to - you.be sure to backup + your old configuration if it is valuable to you. See the note to - upgradersnote to upgraders section below.
RPMs can be installed with RPMs can be installed with rpm -Uvh privoxy-3.0.3-1.rpmrpm -Uvh privoxy-3.0.13-1.rpm, and will use ntsysv, or similar methods. Note that SuSE will -automatically start Privoxy in the boot process.
, or similar methods.If you have problems with failed dependencies, try rebuilding the SRC RPM: - rpm --rebuild privoxy-3.0.3-1.src.rpmrpm --rebuild privoxy-3.0.13-1.src.rpm. This will use your locally installed libraries and RPM version.
Junkbuster - automatically, before installing Privoxy.
2.1.2. Debian2.1.2. Debian and UbuntuDEBs can be installed with DEBs can be installed with apt-get install privoxyapt-get install privoxy, and will use
Just double-click the installer, which will guide you through the installation process. You will find the configuration files - in the same directory as you installed Privoxy in. We do not - use the registry of Windows.
Privoxy in.Version 3.0.5 beta introduced full Windows service + functionality. On Windows only, the Privoxy + program has two new command line arguments to install and uninstall + Privoxy as a service.
--install[:service_name] +
--uninstall[:service_name] +
After invoking Privoxy with + --install, you will need to bring up the + Windows service console to assign the user you + want Privoxy to run under, and whether or not you + want it to run whenever the system starts. You can start the + Windows services console with the following + command: services.msc. If you do not take the manual step + of modifying Privoxy's service settings, it will + not start. Note too that you will need to give Privoxy a user account that + actually exists, or it will not be permitted to + write to its log and configuration files.
Create a new directory, Create a new directory, cdcd to it, then unzip and untar the archive. For the most part, you'll have to figure out where things go.
2.1.6. Mac OSX2.1.6. Mac OS XUnzip the downloaded file (you can either double-click on the file - from the finder, or from the desktop if you downloaded it there). - Then, double-click on the package installer icon named - Privoxy.pkg - and follow the installation process. - Privoxy will be installed in the folder - /Library/Privoxy. - It will start automatically whenever you start up. To prevent it from - starting automatically, remove or rename the folder - /Library/StartupItems/Privoxy.
Unzip the downloaded file (you can either double-click on the zip file + icon from the Finder, or from the desktop if you downloaded it there). + Then, double-click on the package installer icon and follow the + installation process.To start Privoxy by hand, double-click on - The privoxy service will automatically start after a successful + installation (in addition to every time your computer starts up). To + prevent the privoxy service from automatically starting when your + computer starts up, remove or rename the folder named + StartPrivoxy.command in the - /Library/Privoxy folder. - Or, type this command in the Terminal:
/Library/Privoxy/StartPrivoxy.command - |
You will be prompted for the administrator password.
To manually start or stop the privoxy service, use the Privoxy Utility + for Mac OS X. This application controls the privoxy service (e.g. + starting and stopping the service as well as uninstalling the software).Privoxy is part of FreeBSD's Ports Collection, you can build and install + it with cd /usr/ports/www/privoxy; make install clean.
If you don't use the ports, you can fetch and install + the package with pkg_add -r privoxy.
The port skeleton and the package can also be downloaded from the + File Release + Page, but there's no reason to use them unless you're interested in the + beta releases which are only available there.
Gentoo source packages (Ebuilds) for Privoxy under Gentoo just do - first emerge rsyncemerge --sync to get the latest changes from the - Portage tree. With emerge privoxyemerge privoxy you install the latest version.
, the documentation is in /usr/share/doc/privoxy-3.0.3/usr/share/doc/privoxy-3.0.13 and the Log directory is in Privoxy sources - is to download the source tarball from our project +>project download page.
the CVS repository or simply download the nightly CVS - tarball.
.To build gcc are required.
When building from a source tarball (either release version or - nightly CVS - tarball), first unpack the source:
When building from a source tarball, + first unpack the source:
tar xzvf privoxy-3.0.3-src* [.tgz or .tar.gz] - cd privoxy-3.0.3tar xzvf privoxy-3.0.13-beta-src.tar.gz + cd privoxy-3.0.13-beta |
For retrieving the current CVS sources, you'll need CVS installed. - Note that sources from CVS are development quality, and may not be - stable, or well tested. To download CVS source:
For retrieving the current CVS sources, you'll need a CVS client installed. + Note that sources from CVS are typically development quality, and may not be + stable, or well tested. To download CVS source, check the Sourceforge + documentation, which might give commands like:
cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login - cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current +> cvs -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa login + cvs -z3 -d:pserver:anonymous@ijbswa.cvs.sourceforge.net:/cvsroot/ijbswa co current cd current | , which will
contain the source tree.
privoxy:*:7777:7777:privoxy proxy:/no/home:/no/shell |
And then /etc/group, like:
privoxy:*:7777: |
Some binary packages may do this for you.
Then, to build from either unpacked tarball or CVS source:
If you have gnu make, you can have the first four steps +> Using GNU make, you can have the first four steps automatically done for you by just typing:
./configure --disable-toggle --disable-editor --disable-force |
Then build as above. In Privoxy 3.0.7 and later, all of these options +can also be disabled through the configuration file.
WARNING: If installing as root, the install will fail + unless a non-root user or group is specified, or a privoxy + user and group already exist on the system. If a non-root user is specified, + and no group, then the installation will try to also use a group of the same name + as "user". If a group is specified (and no user), then the + support files will be installed as writable by that group, and owned by the + user running the installation.
configure accepts --with-user and + --with-group options for setting user and group ownership + of the configuration files (which need to be writable by the daemon). The + specified user must already exist. When starting + Privoxy, it must be run as this same user to + insure write access to configuration and log files!
Alternately, you can specify user and group + on the make command line, but be sure both already exist:
make -s install USER=privoxy GROUP=privoxy |
The default installation path for make install is + /usr/local. This may of course be customized with + the various ./configure path options. If you are doing + an install to anywhere besides /usr/local, be + sure to set the appropriate paths with the correct configure options + (./configure --help). Non-privileged users must of course + have write access permissions to wherever the target installation is going.
If you do install to /usr/local, the install will use + sysconfdir=$prefix/etc/privoxy by default. All other + destinations, and the direct usage of --sysconfdir flag + behave like normal, i.e. will not add the extra privoxy + directory. This is for a safer install, as there may already exist another + program that uses a file with the "config" name, and thus makes + /usr/local/etc cleaner.
If installing to /usr/local, the documentation will go + by default to $prefix/share/doc. But if this directory + doesn't exist, it will then try $prefix/doc and install + there before creating a new $prefix/share/doc just for + Privoxy.
Again, if the installs goes to /usr/local, the + localstatedir (ie: var/) will default + to /var instead of $prefix/var so + the logs will go to /var/log/privoxy/, and the pid file + will be created in /var/run/privoxy.pid.
make install will attempt to set the correct values + in config (main configuration file). You should + check this to make sure all values are correct. If appropriate, + an init script will be installed, but it is up to the user to determine + how and where to start Privoxy. The init + script should be checked for correct paths and values, if anything other than + a default install is done.
If install finds previous versions of local configuration files, most of + these will not be overwritten, and the new ones will be installed with a + "new" extension. default.action and default.filter + will be overwritten. You will then need + to manually update the other installed configuration files as needed. The + default template files will be overwritten. If you have + customized, local templates, these should be stored safely in a separate + directory and defined in config by the + "templdir" directive. It is of course wise to always back-up any + important configuration files "just in case". If a previous + version of Privoxy is already running, you will + have to restart it manually.
For more detailed instructions on how to build Redhat RPMs, Windows self-extracting installers, building on platforms with special requirements etc, please consult the developer manual.
actions file (as a separate package, ijbswa-announce@lists.sourceforge.net.In order not to loose your personal changes and adjustments when updating - to the latest In order not to lose your personal changes and adjustments when updating + to the latest default.actiondefault.action file we strongly recommend that you use that you use user.action and + user.action for your - customization of user.filter for your local + customizations of Privoxy. See the NextNote to UpgradersWhat's New in this Release