Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#3680 closed Enhancement (invalid)

please make transmission-remote more usable from scripts

Reported by: fejesjoco Owned by:
Priority: Normal Milestone: None Set
Component: Daemon Version: 2.11
Severity: Normal Keywords:


Some ideas:

  • ability to set authentication data from an environment variable (so that I can do AUTH=user:pwd transmission-remote and it won't be visible in ps)
  • print torrent hashes instead of ID's (it's a stable identifier, useful if a script runs longer and does a lot of stuff)
  • unformatted, easily parsable output (print all sizes in bytes, remaining time in seconds, no padding spaces)

If you like these ideas, I'd be happy to send patches myself.

Attachments (1)

authenv.patch (2.4 KB) - added by fejesjoco 11 years ago.
authenv command line option

Download all attachments as: .zip

Change History (8)

comment:1 Changed 11 years ago by fejesjoco

Forgot to mention: of course I mean additional options to do these stuff, not override the current behavior.

comment:2 Changed 11 years ago by Friznard

others have made similar requests in the past and been shot down. the usual response is to use the rpc api. if you're not a typical user, you won't get much love from this client.

comment:3 Changed 11 years ago by starmoon

for the first, I suggest to make it possiable to not using password for local connection.

comment:4 Changed 11 years ago by livings124

  • Milestone changed from 2.12 to None Set

Don't set milestones without a patch.

Changed 11 years ago by fejesjoco

authenv command line option

comment:5 Changed 11 years ago by fejesjoco

Okay, here's a start. It adds the authenv command line option, docs included. The patch is against trunk. Tested and WFM.

comment:6 Changed 11 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

The patch looks fine, but from a bookkeeping standpoint I have a problem with this ticket having open-ended goals. Please open a separate ticket for each feature/bug/etc. For example I could apply this patch, and it would be a completed feature, but the ticket couldn't be milestoned or closed because of other tangentally-related requests.

comment:7 Changed 11 years ago by fejesjoco

Fair enough, #3763 created.

Note: See TracTickets for help on using tickets.