X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fstartup.html;h=f3c42acc27670550adc927fda98944e3564a2b42;hp=96baff2964b60afb132b919c9755234aa0798dad;hb=3db7a58b2bbed7b6356b2a0600e93ec4f2846499;hpb=0a3750f6302df8349b5be2e15a9a4fefe3c35889 diff --git a/doc/webserver/user-manual/startup.html b/doc/webserver/user-manual/startup.html index 96baff29..f3c42acc 100644 --- a/doc/webserver/user-manual/startup.html +++ b/doc/webserver/user-manual/startup.html @@ -1,13 +1,13 @@ +
Privoxy User Manual | Privoxy 3.0.17 User Manual|
---|---|
Prev | Next |
- # /usr/sbin/privoxy /etc/privoxy/config# /etc/rc.d/init.d/privoxy start |
See below for other command line options.
Or ...An init script is provided for SuSE and Red Hat.
For for SuSE: rcprivoxy start
For Red Hat and Debian: /etc/rc.d/init.d/privoxy start
# service privoxy start |
If no configuration file is specified on the command line, - We use a script. Note that Debian typically starts Privoxy will look for a file named +> upon booting per + default. It will use the file config in the current directory. Except on Win32 where - it will try config.txt. If no file is specified on the - command line and no default configuration file can be found, - /etc/privoxy/config as its main configuration + file.
# /etc/init.d/privoxy start |
Click on the Privoxy will fail to start.
The included default configuration files should give a reasonable starting - point. Most of the per site configuration is done in the - "actions" files. These are where various cookie actions are - defined, ad and banner blocking, and other aspects of - Icon to start Privoxy configuration. There are several such - files included, with varying levels of aggressiveness.
You will probably want to keep an eye out for sites for which you may prefer - persistent cookies, and add these to your actions configuration as needed. By - default, most of these will be accepted only during the current browser - session (aka "session cookies"), unless you add them to the - configuration. If you want the browser to handle this instead, you will need - to edit . If no configuration file is + specified on the command line, Privoxy will look + for a file named user.action (or through the web based interface) - and disable this feature. If you use more than one browser, it would make - more sense to let config.txt. Note that Windows will + automatically start Privoxy handle this. In which - case, the browser(s) should be set to accept all cookies.
Another feature where you will probably want to define exceptions for trusted - sites is the popup-killing (through the +popup and - +filter{popups} actions), because your favorite shopping, - banking, or leisure site may need popups (explained below).
when the system starts if you chose that option + when installing.Privoxy is HTTP/1.1 compliant, but not all of - the optional 1.1 features are as yet supported. In the unlikely event that - you experience inexplicable problems with browsers that use HTTP/1.1 per default - (like can run with full Windows service functionality. + On Windows only, the Mozilla or recent versions of I.E.), you might - try to force HTTP/1.0 compatibility. For Mozilla, look under Edit -> - Preferences -> Debug -> Networking. - Alternatively, set the "+downgrade-http-version" config option in - default.action which will downgrade your browser's HTTP - requests from HTTP/1.1 to HTTP/1.0 before processing them.
After running Privoxy program has two new command line arguments + to install and uninstall Privoxy for a while, you can - start to fine tune the configuration to suit your personal, or site, - preferences and requirements. There are many, many aspects that can - be customized. "Actions" - can be adjusted by pointing your browser to +> as a service. See the http://config.privoxy.org/ - (shortcut: http://p.p/), - and then follow the link to "View & Change the Current Configuration". - (This is an internal page and does not require Internet access.)
Windows Installation + instructions for details.Example Unix startup command:
# /usr/sbin/privoxy /etc/privoxy/config |
In fact, various aspects of During installation, Privoxy - configuration can be viewed from this page, including - current configuration parameters, source code version numbers, - the browser's request headers, and "actions" that apply - to a given URL. In addition to the actions file - editor mentioned above, is configured to + start automatically when the system restarts. You can start it manually by + double-clicking on the Privoxy can also - be turned "on" and "off" (toggled) from this page.
icon in the + Privoxy folder.After downloading the privoxy software, unzip the downloaded file by + double-clicking on the zip file icon. Then, double-click on the + installer package icon and follow the installation process.
The privoxy service will automatically start after a successful + installation. In addition, the privoxy service will automatically + start 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.
A simple application named Privoxy Utility has been created which + enables administrators to easily start and stop the privoxy service.
In addition, the Privoxy Utility presents a simple way for + administrators to edit the various privoxy config files. A method + to uninstall the software is also available.
An administrator username and password must be supplied in order for + the Privoxy Utility to perform any of the tasks.
If you encounter problems, try loading the page without +> Start Privoxy (with RUN <>NIL:) in your + startnet script (AmiTCP), in + s:user-startup (RoadShow), as startup program in your + startup script (Genesis), or as startup action (Miami and MiamiDx). Privoxy. If that helps, enter the URL where - you have the problems into the browser - based rule tracing utility. See which rules apply and why, and - then try turning them off for that site one after the other, until the problem - is gone. When you have found the culprit, you might want to turn the rest on - again.
If the above paragraph sounds gibberish to you, you might want to read more about the actions concept - or even dive deep into the Appendix - on actions.
will automatically quit when you quit your + TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that + Privoxy is still running).If you can't get rid of the problem at all, think you've found a bug in - Privoxy, want to propose a new feature or smarter rules, please see the - section "Contacting the - Developers" below.
A script is again used. It will use the file /etc/privoxy/config + as its main configuration file.
/etc/init.d/privoxy start + |
Note that Privoxy is not automatically started at + boot time by default. You can change this with the rc-update + command.
+
rc-update add privoxy default + |
--version
--help
--no-daemon
--pidfile FILE
-
On startup, write the process ID to On startup, write the process ID to FILE. Delete the
- FILE
on exit. Failure to create or delete the
- FILE is non-fatal. If no is non-fatal. If no FILE
option is given, no PID file will be used. Unix only.
--user USER[.GROUP] -
After (optionally) writing the PID file, assume the user ID of - USER, and if included the GID of GROUP. Exit if the privileges are not sufficient to do so. Unix only.
--chroot +
Before changing to the user ID given in the --user option, + chroot to that user's home directory, i.e. make the kernel pretend to the Privoxy + process that the directory tree starts there. If set up carefully, this can limit + the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy. + Unix only. +
--pre-chroot-nslookup hostname +
Specifies a hostname to look up before doing a chroot. On some systems, initializing the + resolver library involves reading config files from /etc and/or loading additional shared + libraries from /lib. On these systems, doing a hostname lookup before the chroot reduces + the number of files that must be copied into the chroot tree. +
For fastest startup speed, a good value is a hostname that is not in /etc/hosts but that + your local name server (listed in /etc/resolv.conf) can resolve without recursion + (that is, without having to ask any other name servers). The hostname need not exist, + but if it doesn't, an error message (which can be ignored) will be output. +
configfile
If no If no configfile is included on the command line,
On MS Windows only there are two additional + command-line options to allow Privoxy to install and + run as a service. See the +Window Installation section +for details.