[tahoe-dev] [tahoe-lafs] #71: "client node probably started"

[tahoe-lafs]

#71: "client node probably started"
----------------------------+-----------------------------------------------
 Reporter:  zooko           |           Owner:  warner    
     Type:  enhancement     |          Status:  assigned  
 Priority:  minor           |       Milestone:  eventually
Component:  code-nodeadmin  |         Version:  0.7.0     
 Keywords:                  |   Launchpad_bug:            
----------------------------+-----------------------------------------------

Comment(by warner):

 Incidentally, I just learned that modern twistd can be run as a library.
 See http://divmod.org/trac/browser/trunk/Axiom/axiom/scripts/axiomatic.py
 for an example. This would make it easier to avoid the extra subprocess,
 and might make it easier to provide a more confident answer to this
 ticket.

 In general, if we can instantiate the Client before the fork, then the
 parent process can be sure that:

  1. the child was able to load all the correct Tahoe code, and import all
 the dependencies
  2. the tahoe.cfg file was well-formed and none of its values caused
 immediate problems

 To feel confident that the Client actually got started, we'll need to
 establish some form of communication between the "tahoe start" parent and
 the actual node process, whether that means tailing the logfile or
 connecting to the control.furl .

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/71#comment:14>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid