Hi Björn!
On Tue, 03 Mar 2009, Björn Påhlsson wrote:
> If privoxy fails to start (at least when there are missing action
> files), then there is no indication from the start script used by
> invoke-rc.d, and invoke-rc.d doesnt return any error exit code.
>
> # invoke-rc.d privoxy start
> # echo $?
> 0
Very strange, it should at least output anything:
# invoke-rc.d privoxy stop
Stopping filtering proxy server: privoxy.
# mv /etc/privoxy/default.action /etc/privoxy/default.action.ignore
# invoke-rc.d privoxy start
Starting filtering proxy server: privoxy failed!
# mv /etc/privoxy/default.action.ignore /etc/privoxy/default.action
# invoke-rc.d privoxy start
Starting filtering proxy server: privoxy.
# ps auxww | grep privoxy
privoxy 18123 0.2 0.0 21252 1340 ? Ss 21:42 0:00
/usr/sbin/privoxy --pidfile /var/run/privoxy.pid --user privoxy
/etc/privoxy/config
root 18130 0.0 0.0 7036 764 pts/3 S+ 21:42 0:00 grep privoxy
> # /usr/sbin/privoxy
> Mar 03 14:40:09.675 7fde0d1096f0 Fatal error: can't check configuration file
> '//config': No such file or directory
Okay, the missing config file has to be written to stderr, because the
log file is configured in the config file. In contrast to this, the
missing action file is logged to /var/log/privoxy/logfile. But there
should be a message that privoxy is started. Maybe there exists some
problem with your lsb-base package, which is used in this version of
privoxy, but you seem to have installed the same version that I have
here.
Tschoeeee
Roland
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
