Your message dated Sun, 18 Jun 2006 02:45:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#338424: tor: /etc/init.d/tor doesn't signal failure if
process does not start
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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 something wrong.
EXAMPLE RUN
# sh -x /etc/init.d/tor start
+ set -e
...
+ echo 'Starting tor daemon: tor...'
Starting tor daemon: tor...
+ ulimit -n 4096
+ start-stop-daemon --start --quiet --oknodo --chuid debian-tor:debian-tor
--pidfile /var/run/tor/tor.pid --exec /usr/sbin/tor --
Nov 10 10:34:08.186 [notice] Tor v0.1.0.15. This is experimental software. Do
not rely on it for strong anonymity.
+ echo done.
done.
+ exit 0
[EMAIL PROTECTED]:~# echo $?
0
[EMAIL PROTECTED]:~# /usr/sbin/tor -l info
Nov 10 10:34:43.464 [notice] Tor v0.1.0.15. This is experimental software. Do
not rely on it for strong anonymity.
Nov 10 10:34:43.468 [warn] /var/lib/tor is not owned by this UID (0). You must
fix this to proceed.
Nov 10 10:34:43.469 [err] options_act(): Couldn't access/create private data
directory /var/lib/tor
Nov 10 10:34:43.470 [err] init_from_config(): Acting on config options left us
in a broken state. Dying.
[EMAIL PROTECTED]:~# echo $?
1
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)
Versions of packages tor depends on:
ii adduser 3.77 Add and remove users and groups
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libevent1 1.1a-1 An asynchronous event notification
ii libssl0.9.8 0.9.8a-3 SSL shared libraries
ii tsocks 1.8beta5-2 transparent network access through
ii zlib1g 1:1.2.3-4 compression library - runtime
Versions of packages tor recommends:
pn privoxy <none> (no description available)
pn socat <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 11 Nov 2005, Peter Palfrader wrote:
> "Cannot assign requested address" is what strerror says, it's not like
> the Tor developers picked it.
>
> In 0.1.1.x the error message also includes the IP address, so I guess
> that's good enough too.
>
> ./src/or/connection.c: warn(LD_NET, "Could not bind to %s:%u: %s",
> address, usePort,
0.1.1.x is in unstable now and it has the better error message.
Closing.
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--- End Message ---
