[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2263: Issue starting/stopping tahoe on Windows with multi-users

[Tahoe-LAFS]

#2263: Issue starting/stopping tahoe on Windows with multi-users
----------------------------+----------------------------------------------
     Reporter:  CyberAxe    |      Owner:  cyberaxe
         Type:  defect      |     Status:  new
     Priority:  normal      |  Milestone:  undecided
    Component:  code-       |    Version:  1.10.0
  nodeadmin                 |   Keywords:  basedir furl windows multi-users
   Resolution:              |
Launchpad Bug:              |
----------------------------+----------------------------------------------
Changes (by daira):

 * keywords:  basedir furl windows mutli-users => basedir furl windows
     multi-users
 * component:  unknown => code-nodeadmin


Comment:

 It makes sense to me that `tahoe stop` would have the same default as
 `tahoe start` for what basedir is operates on. We also need to think about
 compatibility with existing usage habits and scripts. We could potentially
 add a `tahoe stop --all`, however its implementation would have to be
 platform dependent (using either `ps` or `/proc` on Unix, and I-don't
 -know-what on Windows.)

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