TOR "Could not bind To,127.0.0.1:9050:under Ubuntu

################################
# If the Could not bind to 127.0.0.1:9050:address already on use appears. Is Tor already running?
################################

The following error occurred while starting the Vidalia log:

Opening Socks Listener on 127.0.0.1:9050

Could not bind to 127.0.0.1:9050:address already on use. Is Tor already running?

Failed to Parse/validate config:failed to bind one of the listener ports.

Reading config Failed–see warnings above.

This is because the Tor service automatically comes up when the system starts, and Vidalia tries to start Tor again when it starts, and finds that the port is already occupied and how to fix it.

Temporary workaround:
$ sudo service tor stop # or Sudo/etc/init.d/tor stop
Then use Vidalia to start Tor again.

Long-term solution:
$ cd/etc/rc2.d/# set to run Level 2 o'clock to close the corresponding service
$ sudo mv S20privoxy k20privoxy
$ sudo mv S20tor k20tor
Note: In a directory like RCX.D, there are symbolic links,nn representations of snnscript and Knnscript, in order from small to large, K means to stop these services first, and then start services that begin with S