[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2383: CLI option to automatically start and stop a node

[Tahoe-LAFS]

#2383: CLI option to automatically start and stop a node
-----------------------------+-----------------------
     Reporter:  lpirl        |      Owner:
         Type:  enhancement  |     Status:  reopened
     Priority:  normal       |  Milestone:  undecided
    Component:  unknown      |    Version:  1.10.0
   Resolution:               |   Keywords:
Launchpad Bug:               |
-----------------------------+-----------------------

Comment (by daira):

 Replying to [comment:10 lpirl]:
 > …another reason why an integrated behavior should be preferred over a
 shell script.

 Well, not necessarily. The point of #719 is that starting a node and then
 waiting for it to connect to a sufficient number of servers is quite
 expensive in terms of latency. Therefore, if you're going to do several
 operations then you should batch them and start the node only once, then
 (possibly; see below) stop it only once afterward. This lends itself more
 to a script.

 I realize now that I've been expecting most users to leave a gateway node
 running semi-permanently, even though the docs don't actually say you're
 expected to do that.

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