[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #4833 [Vidalia]: Vidalia should set __ReloadTorrcOnSIGHUP to 0 if it can't write its torrc file

#4833: Vidalia should set __ReloadTorrcOnSIGHUP to 0 if it can't write its torrc
file
------------------------+---------------------------------------------------
    Reporter:  arma     |       Owner:  chiiph  
        Type:  defect   |      Status:  reopened
    Priority:  normal   |   Milestone:          
   Component:  Vidalia  |     Version:          
  Resolution:           |    Keywords:          
      Parent:           |      Points:          
Actualpoints:           |  
------------------------+---------------------------------------------------
Changes (by arma):

  * status:  closed => reopened
  * resolution:  fixed =>


Comment:

 If the policy is to put features into 0.3.x and only fix important bugs in
 0.2.x, I think we should reconsider leaving this one out of 0.2.x. It is
 burning many of the Vidalia users on Linux now that the deb supports a
 controlsocket.

 Plus it looks like commit 31428474 isn't that invasive?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4833#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs