-
- <p><b>Privoxy</b> may be invoked with the following command line
- options:</p>
-
- <dl compact>
- <dt><b>--chroot</b></dt>
-
- <dd>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
- <b>Privoxy</b> process that the directory tree starts there. If set up
- carefully, this can limit the impact of possible vulnerabilities in
- <b>Privoxy</b> to the files contained in that hierarchy.</dd>
-
- <dt><b>--config-test</b></dt>
-
- <dd>
- 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.
-
- <p>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).</p>
-
- <p>This option doesn't affect the log setting, combination with
- "--no-daemon" is recommended if a configured log file shouldn't be
- used.</p>
- </dd>
-
- <dt><b>--help</b></dt>
-
- <dd>Print brief usage info and exit.</dd>
-
- <dt><b>--no-daemon</b></dt>
-
- <dd>Don't become a daemon, i.e. don't fork and become process group
- leader, don't detach from controlling tty, and do all logging there.</dd>
-
- <dt><b>--pidfile</b> <i>pidfile</i></dt>
-
- <dd>On startup, write the process ID to <i>pidfile</i>. Delete the
- <i>pidfile</i> on exit. Failure to create or delete the <i>pidfile</i> is
- non-fatal. If no <b>--pidfile</b> option is given, no PID file will be
- used.</dd>
-
- <dt><b>--pre-chroot-nslookup</b> <i>hostname</i></dt>
-
- <dd>Initialize the resolver library using <i>hostname</i> before
- chroot'ing. On some systems this reduces the number of files that must be
- copied into the chroot tree.</dd>
-
- <dt><b>--user</b> <i>user[.group]</i></dt>
-
- <dd>After (optionally) writing the PID file, assume the user ID of
- <i>user</i> and the GID of <i>group</i>, or, if the optional <i>group</i>
- was not given, the default group of <i>user</i>. Exit if the privileges
- are not sufficient to do so.</dd>
-
- <dt><b>--version</b></dt>
-
- <dd>Print version info and exit.</dd>
- </dl>
-
- <p>If the <i>configfile</i> is not specified on the command line,
- <b>Privoxy</b> will look for a file named <i>config</i> in the current
- directory. If no <i>configfile</i> is found, <b>Privoxy</b> will fail to
- start. <a name="lbAE" id="lbAE"> </a></p>
-
+ <p style="margin-left:11%; margin-top: 1em"><b>Privoxy</b> may be invoked with the following command line options:
+ <b><br>
+ −−chroot</b></p>
+ <p style="margin-left:22%;">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 <b>Privoxy</b> process that the directory tree
+ starts there. If set up carefully, this can limit the impact of possible vulnerabilities in <b>Privoxy</b> to the
+ files contained in that hierarchy.</p>
+ <p style="margin-left:11%;"><b>−−config-test</b></p>
+ <p style="margin-left:22%;">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.</p>
+ <p style="margin-left:22%; margin-top: 1em">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).</p>
+ <p style="margin-left:22%; margin-top: 1em">This option doesn’t affect the log setting, combination with
+ "--no-daemon" is recommended if a configured log file shouldn’t be used.</p>
+ <table width="100%" border="0" rules="none" frame="void" cellspacing="0" cellpadding="0">
+ <tr valign="top" align="left">
+ <td width="11%"></td>
+ <td width="9%">
+ <p style="margin-top: 1em" valign="top"><b>−−help</b></p>
+ </td>
+ <td width="2%"></td>
+ <td width="49%">
+ <p style="margin-top: 1em" valign="top">Print brief usage info and exit.</p>
+ </td>
+ <td width="29%"></td>
+ </tr>
+ </table>
+ <p style="margin-left:11%;"><b>−−no-daemon</b></p>
+ <p style="margin-left:22%;">Don’t become a daemon, i.e. don’t fork and become process group leader,
+ don’t detach from controlling tty, and do all logging there.</p>
+ <p style="margin-left:11%;"><b>−−pidfile</b> <i>pidfile</i></p>
+ <p style="margin-left:22%;">On startup, write the process ID to <i>pidfile</i>. Delete the <i>pidfile</i> on exit.
+ Failure to create or delete the <i>pidfile</i> is non-fatal. If no <b>−−pidfile</b> option is given, no
+ PID file will be used.</p>
+ <p style="margin-left:11%;"><b>−−pre-chroot-nslookup</b> <i>hostname</i></p>
+ <p style="margin-left:22%;">Initialize the resolver library using <i>hostname</i> before chroot’ing. On some
+ systems this reduces the number of files that must be copied into the chroot tree.</p>
+ <p style="margin-left:11%;"><b>−−user</b> <i>user[.group]</i></p>
+ <p style="margin-left:22%;">After (optionally) writing the PID file, assume the user ID of <i>user</i> and the GID of
+ <i>group</i>, or, if the optional <i>group</i> was not given, the default group of <i>user</i>. Exit if the
+ privileges are not sufficient to do so.</p>
+ <p style="margin-left:11%;"><b>−−version</b></p>
+ <p style="margin-left:22%;">Print version info and exit.</p>
+ <p style="margin-left:11%; margin-top: 1em">If the <i>configfile</i> is not specified on the command line,
+ <b>Privoxy</b> will look for a file named <i>config</i> in the current directory. If no <i>configfile</i> is found,
+ <b>Privoxy</b> will fail to start.</p><a name="DESCRIPTION"></a>