4 >Starting Privoxy</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy 2.9.20 User Manual"
10 HREF="index.html"><LINK
12 TITLE="Quickstart to Using Privoxy"
13 HREF="quickstart.html"><LINK
15 TITLE="Privoxy Configuration"
16 HREF="configuration.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy 2.9.20 User Manual</TH
46 HREF="quickstart.html"
59 HREF="configuration.html"
79 > Before launching <SPAN
82 > for the first time, you
83 will want to configure your browser(s) to use
87 > as a HTTP and HTTPS proxy. The default is
88 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions
89 used port 8000). This is the one configuration step that must be done!</P
91 > Please note that <SPAN
94 > can only proxy HTTP and
95 HTTPS traffic. It will not work with FTP or other protocols.</P
104 >Figure 2. Proxy Configuration (Mozilla)</B
110 SRC="../images/proxy_setup.jpg"
111 ALT="[ Screenshot of Mozilla Proxy Configuration ]"
127 >), this can be set under:</P
129 CLASS="LITERALLAYOUT"
134 |_ <br>
135 <SPAN
139 |_ <br>
140 <SPAN
144 |_ <br>
145 <SPAN
149 |_ <br>
150 <SPAN
157 >Internet Explorer</SPAN
160 CLASS="LITERALLAYOUT"
165 |_ <br>
166 <SPAN
168 >Internet Properties</SPAN
170 |_ <br>
171 <SPAN
175 |_ <br>
176 <SPAN
184 > and fill in the appropriate info
185 (Address: 127.0.0.1, Port: 8118). Include HTTPS (SSL), if you want HTTPS
186 proxy support too. </P
188 > After doing this, flush your browser's disk and memory caches to force a
189 re-reading of all pages and to get rid of any ads that may be cached. You
190 are now ready to start enjoying the benefits of using
199 > is typically started by specifying the
200 main configuration file to be used on the command line. If no configuration
201 file is specified on the command line, <SPAN
205 will look for a file named <TT
209 directory. Except on Win32 where it will try <TT
219 >5.1. Red Hat and Conectiva</A
222 > We use a script. Note that Red Hat does not start Privoxy upon booting per
223 default. It will use the file <TT
225 >/etc/privoxy/config</TT
227 its main configuration file.</P
237 > # /etc/rc.d/init.d/privoxy start</PRE
252 > We use a script. Note that Debian starts Privoxy upon booting per
253 default. It will use the file
256 >/etc/privoxy/config</TT
257 > as its main configuration
268 > # /etc/init.d/privoxy start</PRE
283 >We use a script. It will use the file <TT
285 >/etc/privoxy/config</TT
287 as its main configuration file. Note that SuSE starts Privoxy upon booting
298 > # rcprivoxy start</PRE
313 >Click on the Privoxy Icon to start Privoxy. If no configuration file is
314 specified on the command line, <SPAN
321 >. Note that Windows will
322 automatically start Privoxy upon booting you PC.</P
330 >5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</A
333 >Example Unix startup command:</P
343 > # /usr/sbin/privoxy /etc/privoxy/config</PRE
358 > During installation, <SPAN
362 start automatically when the system restarts. You can start it manually by
363 double-clicking on the <SPAN
381 > During installation, <SPAN
385 start automatically when the system restarts. To start Privoxy by hand,
386 double-click on the <TT
388 >StartPrivoxy.command</TT
392 >/Library/Privoxy</TT
393 > folder. Or, type this command
404 > /Library/Privoxy/StartPrivoxy.command
411 > You will be prompted for the administrator password.</P
425 > (with RUN <>NIL:) in your
429 > script (AmiTCP), in
433 > (RoadShow), as startup program in your
434 startup script (Genesis), or as startup action (Miami and MiamiDx).
438 > will automatically quit when you quit your
439 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
443 > is still running).</P
454 > A script is again used. It will use the file <TT
458 > as its main configuration file.</P
468 > /etc/init.d/privoxy start
478 > is not automatically started at
479 boot time by default. You can change this with the <TT
494 > rc-update add privoxy default
507 >5.10. Command Line Options</A
513 > may be invoked with the following
514 command-line options:</P
527 > Print version info and exit. Unix only.
538 > Print short usage info and exit. Unix only.
549 > Don't become a daemon, i.e. don't fork and become process group
550 leader, and don't detach from controlling tty. Unix only.
562 > On startup, write the process ID to <I
569 > on exit. Failure to create or delete the
573 > is non-fatal. If no <I
577 option is given, no PID file will be used. Unix only.
584 >--user USER[.GROUP]</I
589 > After (optionally) writing the PID file, assume the user ID of
593 >, and if included the GID of GROUP. Exit if the
594 privileges are not sufficient to do so. Unix only.
608 > is included on the command line,
612 > will look for a file named
616 > in the current directory (except on Win32
617 where it will look for <SPAN
621 full path to avoid confusion. If no config file is found,
625 > will fail to start.
647 HREF="quickstart.html"
663 HREF="configuration.html"
672 >Quickstart to Using <SPAN