- <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>
+ <b>--chroot</b>
+ 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.