#986 closed enhancement (wontfix)

'tahoe run' and 'tahoe start' should be one command

Reported by: JeremyVisser Owned by:
Priority: minor Milestone: undecided
Component: code-frontend-cli Version: 1.6.0
Keywords: usability docs tahoe-run Cc:
Launchpad Bug:

Description (last modified by exarkun)

Initially, I was slightly confused by the difference between tahoe run and tahoe start. Of course, reading the docs clears it up, but I can foresee getting the two mixed up in future, especially during late nights. :)

Generalising from experience, most applications either fork by default and have a flag to stop it forking, or don't fork by default, and have a flag to fork if the user desires. So it's a switch, rather than separate commands.

I suggest adding either the tahoe start --daemon or tahoe start --foreground switches. The former if you want foreground to be default, or the latter if you want daemonising to be default.

Not sure if it conflicts with any other switches, but -d and -f are choicy short versions of the above.

Any thoughts?

Attachments (1)

nodaemon.patch (825 bytes) - added by np at 2011-11-10T15:31:52Z.

Download all attachments as: .zip

Change History (9)

comment:1 Changed at 2010-03-09T06:57:23Z by JeremyVisser

  • Keywords usability added

comment:2 Changed at 2010-03-14T03:56:38Z by warner

I like it. "tahoe start" should continue to be the daemonizing form, but I'd be happy to see "tahoe run" replaced with "tahoe start -n/--nodaemon" (just like twistd accepts).

comment:3 Changed at 2010-03-15T09:20:48Z by JeremyVisser

Sounds good to me.

comment:4 Changed at 2010-04-04T00:02:40Z by davidsarah

  • Keywords docs added

I don't really see the advantage. Do people really find "tahoe start --nodaemon" easier to remember than "tahoe run"? If we added the former, we'd probably still keep the latter (for compatibility with user habits and scripts), and it seems undesirable to me to have two ways of doing this.

comment:5 Changed at 2010-04-04T02:58:21Z by zooko

  1. Familiarity: Jeremy Visser expected a switch to control this rather than a different command. As Brian mentioned, twistd has a switch to control this.
  1. Self-documentation: someone who knows to run tahoe start might wonder how to run it without daemonizing, run tahoe start --help and see the --nodaemon switch. If we're not going to add that switch then at least we should add a sentence after the list of options in tahoe start --help which says "See also the tahoe run command.", but that seems like slightly worse documentation than an option.
  1. After all, isn't it logically a option of the "start yourself" command rather than a different command?

comment:6 Changed at 2010-07-21T16:44:52Z by zooko

  • Keywords tahoe-run added

Changed at 2011-11-10T15:31:52Z by np

comment:7 Changed at 2011-11-10T15:32:27Z by np

Here is a three lines patch to support tahoe start --nodaemon.

This is done by simply relaying the option to twisted. The patch also sets the default umask since twistd --nodaemon has also the effect of no longer setting the default umask.

comment:8 Changed at 2020-01-18T00:27:43Z by exarkun

  • Description modified (diff)
  • Resolution set to wontfix
  • Status changed from new to closed

"tahoe start" is now deprecated. Only "tahoe run" will remain.

Note: See TracTickets for help on using tickets.