Please use local user's path when starting Tor

Vidalia is configured to use a certain controlsocket, and it will use it, either to connect to a currently running Tor instance, or to start a new one using that specific value.

This presents a few cases in which you couldn't and also shouldn't do that, one of them might be this:

You are already running a Tor instance which you are not supposed to hook against to. This is the case of a multiuser system in which many different users will start their own Tor instances, i.e, for privacy reasons. In this case, permissions wont allow Vidalia to hang to that controlsocket, and it will simply fail to start.

One possible way to avoid this could be as simple as:

• If you couldn't connect to a running Tor instance (because foobar reasons), simply start a new one, but override controlsocket to, for example, ~/.tor/control/socket.

Bare in mind that the directory containing the socket should be 0700, otherwise Tor will fail to start.