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

Re: Newbie needs help

     On Fri, 24 Jul 2009 14:06:55 +0200 Christian Fromme <kaner@xxxxxxxxxx>
>On Fri, Jul 24, 2009 at 1:58 PM, Bob
>Williams<security@xxxxxxxxxxxxxxxxxxxxx> wrote:
>> 12:53 barrowhillfarm:~> killall tor
>> 12:53 barrowhillfarm:~> tor -f /etc/tor/torrc
>> Jul 24 12:54:15.469 [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 12:54:15.470 [notice] Initialized libevent version 1.4.5-stable using
>> method epoll. Good.
>> Jul 24 12:54:15.470 [notice] Opening Socks listener on
>> Jul 24 12:54:15.470 [warn] Could not bind to Address already
>> in use. Is Tor already running?
>> Jul 24 12:54:15.470 [warn] Failed to parse/validate config: Failed to bind one
>> of the listener ports.
>> Jul 24 12:54:15.470 [err] Reading config failed--see warnings above.
>> 12:54 barrowhillfarm:~>
>> I know there is nothing else trying to use port 9050 as /etc/services says so:
>> #               9027-9079   Unassigned
>> What next?
>I guess your Tor is ok. Please follow the instructions provided by others.
>Next time you want to kill Tor, check out its process id (`pidof tor`
>or `ps ax | grep tor | grep -v grep`) and kill that explicitly via
>`kill <pid>`. Make sure you're the same user that started Tor when you
>kill it. Check if its still running afterwards (`ps ax | grep tor |
>grep -v grep`).
     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.

                                  Scott Bennett, Comm. ASMELG, CFIAG
* Internet:       bennett at cs.niu.edu                              *
* "A well regulated and disciplined militia, is at all times a good  *
* objection to the introduction of that bane of all free governments *
* -- a standing army."                                               *
*    -- Gov. John Hancock, New York Journal, 28 January 1790         *