Ubuntu – How to stop tor from starting before Vidalia

networkingtor

I get these errors trying to run tor with vidalia

Apr 19 21:55:15.371 [Notice] Tor v0.2.1.30. This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
Apr 19 21:55:15.372 [Notice] Initialized libevent version 1.4.13-stable using method epoll. Good.
Apr 19 21:55:15.373 [Notice] Opening Socks listener on 127.0.0.1:9050
Apr 19 21:55:15.373 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Apr 19 21:55:15.373 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Apr 19 21:55:15.373 [Error] Reading config failed--see warnings above.

I don't think tor is running. Here is a nmap scan of my localhost

Starting Nmap 5.21 ( http://nmap.org ) at 2011-04-19 21:59 CEST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000050s latency).
Hostname localhost resolves to 2 IPs. Only scanned 127.0.0.1
rDNS record for 127.0.0.1: localhost.localdomain
Not shown: 989 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
53/tcp    open  domain
80/tcp    open  http
139/tcp   open  netbios-ssn
445/tcp   open  microsoft-ds
631/tcp   open  ipp
3128/tcp  open  squid-http
3306/tcp  open  mysql
9000/tcp  open  cslistener
9050/tcp  open  tor-socks
10000/tcp open  snet-sensor-mgmt

I see tor-socks is running here, probably be the cause of the problem. How do I stop this from starting up? I want to use vidalia so I can monitor whats going on.

Best Answer

  • Newer versions of Tor have a file /etc/default/tor.vidalia. It contains three lines:

    if [ -x /usr/bin/vidalia ]; then
            RUN_DAEMON=yes
    fi
    

    You can change the option to no. This will prevent from starting as daemon. Instead Tor will now start when you start Vidalia.

  • Related Question