Bug#338424: tor: /etc/init.d/tor doesn't signal failure if process does not start

2005-11-11 Thread Jari Aalto
Peter Palfrader [EMAIL PROTECTED] writes: severity 338424 normal thanks On Thu, 10 Nov 2005, Jari Aalto wrote: | Package: tor | Version: 0.1.0.15-1.0.1 | Severity: important | | There should not be exit 0 in /etc/init.d/tor to cover all cases of | startup. If process did not start of

Bug#338424: tor: /etc/init.d/tor doesn't signal failure if process does not start

2005-11-11 Thread Peter Palfrader
On Fri, 11 Nov 2005, Jari Aalto wrote: Nov 10 10:34:08.189 [notice] Tor 0.1.0.15 opening log file. Nov 10 10:34:08.190 [notice] Initialized libevent version 1.1a using method epoll Nov 10 10:34:08.192 [warn] connection_create_listener(): Could not bind to port 9050: Cannot

Bug#338424: tor: /etc/init.d/tor doesn't signal failure if process does not start

2005-11-10 Thread Jari Aalto
Package: tor Version: 0.1.0.15-1.0.1 Severity: important There should not be exit 0 in /etc/init.d/tor to cover all cases of startup. If process did not start of if it didn't stop, there should be indication of error. Now it always signals ok - only for admin to find out much later that there is

Bug#338424: tor: /etc/init.d/tor doesn't signal failure if process does not start

2005-11-10 Thread Peter Palfrader
severity 338424 normal thanks On Thu, 10 Nov 2005, Jari Aalto wrote: Package: tor Version: 0.1.0.15-1.0.1 Severity: important There should not be exit 0 in /etc/init.d/tor to cover all cases of startup. If process did not start of if it didn't stop, there should be indication of error.