[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Newbie needs help



On Friday 24 July 2009 13:16:50 Scott Bennett wrote:
>   On UNIX systems, the default signal sent by kill is SIGHUP.  Is that
> default signal different on LINUX systems?  A SIGHUP will not result in
> tor shutting down unless it discovers an error upon rereading torrc.  On
> a UNIX system, "kill -TERM <pid>" should be used.  On FreeBSD systems,
> tor puts its pid into a file called /var/run/tor/tor.pid, so a command
> like "kill -TERM `cat /var/run/tor/tor.pid`" will initiate the shutdown
> sequence, but the tor port in FreeBSD also establishes a script called
> /usr/local/etc/rc.d/tor, so "/usr/local/etc/rc.d/tor stop" will do it, too.
> Changing "stop" to "start" does what it says, and "restart" combines "stop"
> and "start".  I'm surprised a LINUX installation doesn't have some
> equivalent setup, though with different path names to the files involved.

Ah ha! A quick look around this openSUSE linux system reveals /etc/rc.d/tor 
and that accepts the 'stop' option. It tells me that 'tor apparently not 
running (no pid file)'.

However, ps ax | grep tor | grep -v grep says

8829	pts/0	T	0:03 tor -f /etc/tor/torrc

and /etc/rc.d/tor start fails with

13:27 barrowhillfarm:~> /etc/rc.d/tor start
Starting tor daemon
Jul 24 13:27:54.225 [notice] Tor v0.2.0.35. This is experimental software. Do 
not rely on it for strong anonymity. (Running on Linux x86_64)
Jul 24 13:27:54.226 [notice] Initialized libevent version 1.4.5-stable using 
method epoll. Good.
Jul 24 13:27:54.226 [notice] Opening Socks listener on 127.0.0.1:9050
Jul 24 13:27:54.226 [warn] Could not bind to 127.0.0.1:9050: Address already 
in use. Is Tor already running?
Jul 24 13:27:54.226 [warn] Failed to parse/validate config: Failed to bind one 
of the listener ports.
Jul 24 13:27:54.226 [err] Reading config failed--see warnings above.
/usr/bin/torctl start: tor could not be started
startproc:  exit status of parent of /usr/bin/torctl: 3

It looks as if I've messed up my torrc but I've hardly changed anything from 
the defaults, apart from uncommenting a couple of lines. It might help if I 
could see a working torrc file

-- 
Bob