Opened at 2011-09-26T07:17:50Z

Last modified at 2020-01-16T20:15:03Z

#1546 closed enhancement

pass arbitrary options to twistd through the "tahoe" command-line — at Version 4

Reported by: zooko Owned by:
Priority: normal Milestone: eventually
Component: code-frontend-cli Version: 1.9.0a2
Keywords: cli twisted tahoe-start twistd Cc: warner, meskio@…
Launchpad Bug:

Description (last modified by meskio)

comment:4:ticket:1267 Brian suggested:

What if we accepted a syntax like "tahoe start DIR -- ARG1 ARG2" or "tahoe start -- ARG1 ARG2", and passed all the extra ARG1/ARG2 strings into twistd.run()? I'd really like if it we had a way to pass arbitrary twistd arguments, rather than having to hand-code support for each one.

Change History (4)

comment:1 Changed at 2011-10-03T19:51:32Z by davidsarah

  • Keywords tahoe-start added
  • Milestone changed from undecided to eventually

comment:2 Changed at 2011-10-11T02:50:29Z by davidsarah

  • Keywords twistd added

comment:3 Changed at 2012-03-29T19:27:42Z by davidsarah

  • Priority changed from major to normal

comment:4 Changed at 2013-08-07T13:00:04Z by meskio

  • Description modified (diff)

I'm having a look to this idea so I don't implement by hand the --pidfile for the ticket #2045. What I'm not sure is how to make it consistent with tahoe stop. I think tahoe stop should have a --pidfile option, but I'm not sure how. Maybe something like: 

$ tahoe start . -- --pidfile /run/tahoe.pid
$ tahoe stop . --pidfile /run/tahoe.pid

To add '--' to the stop command I think will be confusing, because there is no call after it to twistd to pass the params. But to have it different syntax between start and stop don't looks good.

Any ideas?

Note: See TracTickets for help on using tickets.