On08/05/10 12:26, Marco Stronati wrote: > Vidalia override tor configuration file in order to prevent it from > starting as a daemon. I rarely use vidalia and this way I cannot > start tor using the usual /etc/init.d/tor script. > Please correct this or print a more verbose message like: > "use vidalia to start tor" > Hi Marco Stronati!
In the way I see it, you first install Tor software, and then Vidalia's. In this way, as the last one can control Tor daemon by placing a flagfile, the proper way to deal with this is for you to answer Vidalia's question with the right one :-) I think it's quite straight forward in Vidalia's (re)configuration when It prompts you: Do you want to stop the existing Tor process and let Vidalia start Tor? -No -Yes (just for now) -Yes (and disable it for every boot) <-- This is the only one you should not choose, and in any way, a simple "dpkg-reconfigure vidalia" will prompt you the question again. > because it took me a while to understand the situation. > What about starting by reading README.Debian file next time 8) ? > If users using vidalia don't want the daemon starting then just disable > the service at boot through update-rc.d. > That's not quite accurate. Runlevel symlinks and initscripts are overwritten by package upgrades. In this way we both, Vidalia and Tor software can count on no upgrades screwing each others configuration in a nice way. As I already stated, I don't think this a bug, but due I'm not the one on charge of Tor package, I'll leave this for its maintainer. Greetings, Dererk -- BOFH excuse #449: greenpeace free'd the mallocs
signature.asc
Description: OpenPGP digital signature
