X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fstartup.html;h=efb07462ab07b252e93f051769520b1f494a871a;hp=3e4fa1521a3314570d9e11a1d0b76f0bbd41ab94;hb=7a99a61ab1a3ce0401821aedcd06eba19a698b2a;hpb=07cf496b6edcbd3cf315ec7c48f2c94be27357b1;ds=sidebyside diff --git a/doc/webserver/user-manual/startup.html b/doc/webserver/user-manual/startup.html index 3e4fa152..efb07462 100644 --- a/doc/webserver/user-manual/startup.html +++ b/doc/webserver/user-manual/startup.html @@ -3,40 +3,25 @@ - - Starting Privoxy - + - - +
- + @@ -49,7 +34,7 @@ body { "configuration.html" accesskey="N">Next
Privoxy 3.0.18 User ManualPrivoxy 3.0.25 User Manual
-
+
@@ -62,18 +47,18 @@ body { proxy. The default is 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions used port 8000). This is the one - configuration step that must be - done!

+ configuration step that must + be done!

Please note that Privoxy can only proxy HTTP and HTTPS traffic. It will not work with FTP or other protocols.

- + -

Figure 2. Proxy Configuration Showing Mozilla/Netscape - HTTP and HTTPS (SSL) Settings

+

Figure 2. Proxy Configuration Showing Mozilla/Netscape HTTP and + HTTPS (SSL) Settings

@@ -123,14 +108,14 @@ body { if you want HTTPS proxy support too (sometimes labeled "Secure"). Make sure any checkboxes like "Use the same proxy server for all protocols" is - UNCHECKED. You want only HTTP - and HTTPS (SSL)!

+ UNCHECKED. You want + only HTTP and HTTPS (SSL)!

- + -

Figure 3. Proxy Configuration Showing Internet Explorer - HTTP and HTTPS (Secure) Settings

+

Figure 3. Proxy Configuration Showing Internet Explorer HTTP and + HTTPS (Secure) Settings

@@ -152,30 +137,19 @@ body { will try config.txt.

-

5.1. Red Hat - and Fedora

- -

A default Red Hat installation may not start Privoxy upon boot. It will use the file /etc/privoxy/config as its main configuration file.

- - - - - -
- 
- # /etc/rc.d/init.d/privoxy start
-
-
+

5.1. + Debian

-

Or ...

+

We use a script. Note that Debian typically starts Privoxy upon booting per default. It will use the + file /etc/privoxy/config as its main + configuration file.

- +
@@ -183,19 +157,25 @@ body {
-

5.2. - Debian

+

5.2. + FreeBSD and ElectroBSD

-

We use a script. Note that Debian typically starts Privoxy upon booting per default. It will use the - file /etc/privoxy/config as its main - configuration file.

+

To start Privoxy upon booting, add + "privoxy_enable='YES'" to /etc/rc.conf. + Privoxy will use /usr/local/etc/privoxy/config as its main configuration + file.

+ +

If you installed Privoxy into a + jail, the paths above are relative to the jail root.

- 
- # service privoxy start
+ # /etc/init.d/privoxy start
+

To start Privoxy manually, run:

+ +
@@ -224,20 +204,25 @@ body {
-

5.4. - Solaris, NetBSD, FreeBSD, HP-UX and others

+

5.4. Generic + instructions for Unix derivates (Solaris, NetBSD, HP-UX etc.)

Example Unix startup command:

- 
- # /etc/init.d/privoxy start
+ # service privoxy onestart
+ 
- # /usr/sbin/privoxy /etc/privoxy/config
+ # /usr/sbin/privoxy --user privoxy /etc/privoxy/config
+ +

Note that if you installed Privoxy + through a package manager, the package will probably contain a + platform-specific script or configuration file to start Privoxy upon boot.

@@ -254,80 +239,26 @@ body {

5.6. Mac OS X

-

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.

+ installation (and thereafter every time your computer starts up) + however you will need to configure your web browser(s) to use it. To do + so, configure them to use a proxy for HTTP and HTTPS at the address + 127.0.0.1:8118.

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.

+ computer starts up, remove or rename the file /Library/LaunchDaemons/org.ijbswa.privoxy.plist (on OS X + 10.5 and higher) or the folder named /Library/StartupItems/Privoxy (on OS X 10.4 + 'Tiger').

+ +

To manually start or stop the privoxy service, use the scripts + startPrivoxy.sh and stopPrivoxy.sh supplied in /Applications/Privoxy. + They must be run from an administrator account, using sudo.

-

5.7. - AmigaOS

- -

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 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).

-
- -
-

5.8. - Gentoo

- -

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
-
-
-
-
- -
-

5.9. Command +

5.7. Command Line Options

Privoxy may be invoked with the @@ -335,67 +266,91 @@ body {

  • -

    --version

    +

    --config-test

    + +

    Exit after loading the configuration files before binding to the + listen address. The exit code signals whether or not the + configuration files have been successfully loaded.

    + +

    If the exit code is 1, at least one of the configuration files + is invalid, if it is 0, all the configuration files have been + successfully loaded (but may still contain errors that can + currently only be detected at run time).

    + +

    This option doesn't affect the log setting, combination with + --no-daemon + is recommended if a configured log file shouldn't be used.

    +
    • + +
  • +

    --version

    Print version info and exit. Unix only.

  • -

    --help

    +

    --help

    Print short usage info and exit. Unix only.

  • -

    --no-daemon

    +

    --no-daemon

    Don't become a daemon, i.e. don't fork and become process group leader, and don't detach from controlling tty. Unix only.

  • -

    --pidfile FILE

    +

    --pidfile + FILE

    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 FILE - option is given, no PID file will be used. Unix only.

    + "emphasis">FILE. Delete the + FILE on exit. + Failure to create or delete the FILE is non-fatal. If no FILE option is given, no + PID file will be used. Unix only.

  • -

    --user - USER[.GROUP]

    +

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

    + USER, and if + included the GID of GROUP. Exit if the privileges are not + sufficient to do so. Unix only.

  • -

    --chroot

    +

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

    + "emphasis">--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

    +

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

    +

    Specifies a hostname (for example www.privoxy.org) 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 @@ -406,11 +361,12 @@ body {

  • -

    configfile

    +

    configfile

    -

    If no configfile is - included on the command line, Privoxy will look for a file named +

    If no configfile is included on the command line, + Privoxy will look for a file named "config" in the current directory (except on Win32 where it will look for "config.txt" instead). Specify full path to avoid @@ -422,14 +378,14 @@ body {

    On MS Windows only there are two additional command-line options to allow Privoxy to install and run as a service. See the service. See the Window Installation section for details.

-
+