X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Finstallation.html;h=6dad5a928be5cf7b36a0ed7eefc1b1a7cf68a4b2;hp=118e9231788d2d89c9a9a8668feef8f1401b2365;hb=345a4d0bce0d40df7255eb1aeb2c1473dcb11f47;hpb=3438a9978a79dbb702e70e2e8a80d727f0ddd6e1 diff --git a/doc/webserver/user-manual/installation.html b/doc/webserver/user-manual/installation.html index 118e9231..6dad5a92 100644 --- a/doc/webserver/user-manual/installation.html +++ b/doc/webserver/user-manual/installation.html @@ -7,7 +7,7 @@ NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.79"> +HREF="../p_doc.css"> Privoxy 3.0.7 User ManualPrivoxy 3.0.12 User Manual

RPMs can be installed with rpm -Uvh privoxy-3.0.7-1.rpmrpm -Uvh privoxy-3.0.12-1.rpm, and will use If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm --rebuild privoxy-3.0.7-1.src.rpmrpm --rebuild privoxy-3.0.12-1.src.rpm. This will use your locally installed libraries and RPM version.

2.1.2. Debian2.1.2. Debian and Ubuntu

DEBs can be installed with Privoxy in.

Version 3.0.4 introduced full Version 3.0.5 beta introduced full Windows service @@ -306,7 +309,7 @@ CLASS="SECT3" CLASS="SECT3" >2.1.4. Solaris, NetBSD, HP-UX2.1.4. Solaris

Create a new directory, 2.1.6. Mac OSX2.1.6. Mac OS X

Unzip 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 +> 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.

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 /Library/StartupItems/Privoxy.

To start Privoxy by hand, double-click on - 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). File Release Page, but if you're interested in stable releases only you don't - gain anything by using them., but there's no reason to use them unless you're interested in the + beta releases which are only available there. under Gentoo just do first emerge rsyncemerge --sync to get the latest changes from the Portage tree. With , the documentation is in /usr/share/doc/privoxy-3.0.7/usr/share/doc/privoxy-3.0.12 and the Log directory is in tar xzvf privoxy-3.0.7-beta-src* [.tgz or .tar.gz] - cd privoxy-3.0.7-beta tar xzvf privoxy-3.0.12-stable-src.tar.gz + cd privoxy-3.0.12-stable Then build as above.Then build as above. In Privoxy 3.0.7 and later, all of these options +can also be disabled through the configuration file. "new" extension. default.action, default.filter, and - standard.action extension. default.action and default.filter + will be overwritten. You will then need - to manually update the other installed configuration files as needed. All - template files will be overwritten. If you have customized, local templates, - you should save these first, and in fact it is wise to always save any + 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" 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.