4 >Starting Privoxy</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy User Manual"
11 HREF="index.html"><LINK
13 TITLE="Quickstart to Using Privoxy"
14 HREF="quickstart.html"><LINK
16 TITLE="Privoxy Configuration"
17 HREF="configuration.html"><LINK
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy User Manual</TH
48 HREF="quickstart.html"
62 HREF="configuration.html"
76 NAME="STARTUP">5. Starting <SPAN
81 > Before launching <SPAN
84 > for the first time, you
85 will want to configure your browser(s) to use
89 > as a HTTP and HTTPS proxy. The default is
90 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions
91 used port 8000). This is the one configuration step that must be done!</P
98 >Figure 2. Proxy Configuration (Mozilla)</B
104 SRC="../images/proxy_setup.jpg"></P
118 >), this can be set under:</P
120 CLASS="LITERALLAYOUT"
125 |_ <br>
126 <SPAN
130 |_ <br>
131 <SPAN
135 |_ <br>
136 <SPAN
140 |_ <br>
141 <SPAN
148 >Internet Explorer</SPAN
151 CLASS="LITERALLAYOUT"
156 |_ <br>
157 <SPAN
159 >Internet Properties</SPAN
161 |_ <br>
162 <SPAN
166 |_ <br>
167 <SPAN
175 > and fill in the appropriate info
176 (Address: 127.0.0.1, Port: 8118). Include HTTPS (SSL), if you want HTTPS
177 proxy support too. </P
179 > After doing this, flush your browser's disk and memory caches to force a
180 re-reading of all pages and to get rid of any ads that may be cached. You
181 are now ready to start enjoying the benefits of using
190 > is typically started by specifying the
191 main configuration file to be used on the command line. If no configuration
192 file is specified on the command line, <SPAN
196 will look for a file named <TT
200 directory. Except on Win32 where it will try <TT
209 NAME="START-REDHAT">5.1. Red Hat and Conectiva</H2
211 > We use a script. Note that Red Hat does not start Privoxy upon booting per
212 default. It will use the file <TT
214 >/etc/privoxy/config</TT
216 its main configuration file.</P
226 > # /etc/rc.d/init.d/privoxy start</PRE
237 NAME="START-DEBIAN">5.2. Debian</H2
239 > We use a script. Note that Debian starts Privoxy upon booting per
240 default. It will use the file
243 >/etc/privoxy/config</TT
244 > as its main configuration
255 > # /etc/init.d/privoxy start</PRE
266 NAME="START-SUSE">5.3. SuSE</H2
268 >We use a script. It will use the file <TT
270 >/etc/privoxy/config</TT
272 as its main configuration file. Note that SuSE starts Privoxy upon booting
283 > # rcprivoxy start</PRE
294 NAME="START-WINDOWS">5.4. Windows</H2
296 >Click on the Privoxy Icon to start Privoxy. If no configuration file is
297 specified on the command line, <SPAN
304 >. Note that Windows will
305 automatically start Privoxy upon booting you PC.</P
312 NAME="START-UNICES">5.5. Solaris, NetBSD, FreeBSD, HP-UX and others</H2
314 >Example Unix startup command:</P
324 > # /usr/sbin/privoxy /etc/privoxy/config</PRE
335 NAME="START-OS2">5.6. OS/2</H2
337 > During installation, <SPAN
341 start automatically when the system restarts. You can start it manually by
342 double-clicking on the <SPAN
356 NAME="START-MACOSX">5.7. MAX OSX</H2
358 > During installation, <SPAN
362 start automatically when the system restarts. You can start it manually
363 through the Terminal with these commands:</P
373 > cd /Applications/Privoxy.app
385 NAME="START-AMIGAOS">5.8. AmigaOS</H2
390 > (with RUN <>NIL:) in your
394 > script (AmiTCP), in
398 > (RoadShow), as startup program in your
399 startup script (Genesis), or as startup action (Miami and MiamiDx).
403 > will automatically quit when you quit your
404 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
408 > is still running).</P
415 NAME="CMDOPTIONS">5.9. Command Line Options</H2
420 > may be invoked with the following
421 command-line options:</P
437 > Print version info and exit. Unix only.
451 > Print short usage info and exit. Unix only.
465 > Don't become a daemon, i.e. don't fork and become process group
466 leader, and don't detach from controlling tty. Unix only.
481 > On startup, write the process ID to <SPAN
494 > on exit. Failure to create or delete the
501 > is non-fatal. If no <SPAN
508 option is given, no PID file will be used. Unix only.
517 >--user USER[.GROUP]</I
523 > After (optionally) writing the PID file, assume the user ID of
530 >, and if included the GID of GROUP. Exit if the
531 privileges are not sufficient to do so. Unix only.
551 > is included on the command line,
555 > will look for a file named
559 > in the current directory (except on Win32
560 where it will look for <SPAN
564 full path to avoid confusion. If no config file is found,
568 > will fail to start.
580 SUMMARY="Footer navigation table"
591 HREF="quickstart.html"
609 HREF="configuration.html"
619 >Quickstart to Using <SPAN