[tahoe-lafs-trac-stream] [tahoe-lafs] #2149: "tahoe start" emits an error message when tahoe is already running

[tahoe-lafs]

#2149: "tahoe start" emits an error message when tahoe is already running
--------------------------------+---------------------------------
     Reporter:  zooko           |      Owner:  joeyh
         Type:  enhancement     |     Status:  new
     Priority:  normal          |  Milestone:  undecided
    Component:  code-nodeadmin  |    Version:  1.10.0
   Resolution:                  |   Keywords:  usability error cli
Launchpad Bug:                  |
--------------------------------+---------------------------------

Comment (by gdt):

 The point of start when started being an error is to allow detecting
 incorrect assumptions.  I expected this behavior because most other things
 behave this way - starting daemons by hand, and NetBSD's /etc/rc.d system,
 in which start and stop are errors if the program is or is not running.
 So I propose ensure-start and ensure-stop, which are non-erroring versions
 of start and stop, and which do not output anything if there is nothing to
 be done, and which do not write to stderr if there is no error.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2149#comment:6>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage