[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:  unknown                           |        Version:  1.10.0
 Keywords:  basedir furl windows mutli-users  |  Launchpad Bug:
----------------------------------------------+---------------------------
 Problems:
 When starting Tahoe with --basedir= to overwrite default .tahoe path then
 stopping Tahoe

 Code:

 {{{
 C:\allmydata-tahoe-1.10.0\bin>python tahoe start --basedir=c:\.tahoe\
 STARTING 'c:\.tahoe'

 C:\allmydata-tahoe-1.10.0\bin>python tahoe ls
 BackMeUp
 BackedUp
 Backedup
 Copied
 Copied1
 Copied2
 OneDrive
 StMarysArt.cxml
 _trial_temp
 backup
 home.html
 test
 test\StMarysArt.cxml

 C:\allmydata-tahoe-1.10.0\bin>python tahoe stop
 STOPPING 'C:\Users\Jeremy\.tahoe'
 'C:\Users\Jeremy\.tahoe' does not look like a running node directory (no
 twistd.pid)
 }}}

 Question:

 Is Tahoe designed to run with more than one service running at a time with
 different furls?

 If not:
 If not then I'd like to see Tahoe stop - stop what ever is running.
 Once you start Tahoe with a --basedir all other commands should assume
 that basedir.

 If is:
 Then we need a lot more documentation about how to set this up so it's not
 so confusing which service, furl you're currently interacting with.

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