Frankly, I have no idea what log level I am operating tor at because I am only now trying to work with vidalia and have no idea what it's settings are in that regard. I am trying to use vidalia with its defaults (at least as they are in the mandriva rpm). I DID alter the vidalia conf so that instead of stderr, tor is logging to /usr/local/var/log/tor/debug.log.
It took a while for me to figure out how Tork was doing things. I think it may take at least a little for futzing before I figure out the basics of vidalia too. praedor On Monday 11 May 2009 13:33:49 Jon wrote: > Praedor Atrebates wrote: > > On Saturday 09 May 2009 08:25:30 Andrew Lewman wrote: > >> On Fri, 8 May 2009 13:01:23 -0400 > >> > >> Praedor Atrebates <[email protected]> wrote: > >>> I have had to give up on Tork and am now trying to make vidalia > >>> work. I am unable to get vidalia to assign a password to the control > >>> port. How does one do this short of running vidalia as root? It is > >>> preventing me from being able to support the tor network because I do > >>> not want to run with no protected control port. [...] > > I have just confirmed yet another vidalia problem: the log window, if > > opened, > > > scrolls rapidly and refuses to clear or close after I've opened it while > > vidalia is running. All the buttons in the window become unresponsive > > and the > > > only way to close the window is to click the shutdown X in the window > > corner. > > > After that, in about 5 seconds, I get a message that the message window >> is not > > responding and do I want to terminate the application or keep it >> running (it > > eats up lots of CPU too). I hit "terminate" and it takes vidalia down > with > > > it. > What log level are you running when this occurs? -- "If we have Senators and Congressmen there that can't protect themselves against the evil temptations of lobbyists, we don't need to change our lobbies, we need to change our representatives." - Will Rogers
