[tahoe-lafs-trac-stream] [Tahoe-LAFS] #355: 'tahoe run' should not fail silently

[Tahoe-LAFS]

#355: 'tahoe run' should not fail silently
--------------------------------+---------------------------------------
     Reporter:  drewp           |      Owner:  warner
         Type:  defect          |     Status:  closed
     Priority:  major           |  Milestone:  soon
    Component:  code-nodeadmin  |    Version:  0.9.0
   Resolution:  fixed           |   Keywords:  usability error tahoe-run
Launchpad Bug:                  |
--------------------------------+---------------------------------------
Changes (by exarkun):

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


Old description:

> I use supervisord, so I'd like to run tahoe in the foreground.

New description:

 I use supervisord, so I'd like to run tahoe in the foreground.

--

Comment:

 "tahoe start" and the other daemonization commands are now deprecated
 (https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3273) and "tahoe run" will
 be the preferred and only way to run a tahoe node after that deprecation
 period ends.

 "tahoe run" exits currently with code 1 when there is no runnable node in
 ~/.tahoe.
 When "tahoe run" is used twice against the same node directory, the second
 attempt exits with code 1 and an error like "Another twistd server is
 running, PID ...".

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/355#comment:15>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage