[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
   Resolution:            |   Keywords:  basedir furl windows mutli-users
Launchpad Bug:            |
--------------------------+----------------------------------------------
Description changed by CyberAxe:

Old description:

> 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.

New description:

 Problems:
 When starting Tahoe with --basedir= to overwrite default .tahoe path then
 stopping Tahoe
 This also looks like it might be a bug
 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 stop --basedir=c:\.tahoe\
 STOPPING 'c:\.tahoe'
 'c:\.tahoe' does not look like a running node directory (no twistd.pid)

 C:\allmydata-tahoe-1.10.0\bin>
 }}}

 {{{
 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#comment:1>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage