From: Simon South <simon@simonsouth.net>
To: 44435@debbugs.gnu.org
Cc: simon@simonsouth.net
Subject: [bug#44435] [PATCH 0/1] services: Add Transmission Daemon
Date: Wed, 4 Nov 2020 07:37:31 -0500 [thread overview]
Message-ID: <cover.1604429058.git.simon@simonsouth.net> (raw)
This patch adds a service type for Transmission Daemon, the headless variant
of the Transmission BitTorrent client (https://transmissionbt.com/). Running
the client as a service this way makes it possible to share files over
BitTorrent continuously without requiring a user be logged in.
I've tried to make this as complete as possible but am especially interested
in geting feedback as this is my first attempt at creating a service
definition. A few things to point out:
- I've placed the code in a new "(gnu services file-sharing)" module and the
documentation in a new "File-Sharing Services" section of the manual, only
because these names seemed the most natural to me. ("Peer-to-peer" would be
too broad a categorization, I think, while "BitTorrent" too narrow.)
- The module exports two procedures, "transmission-password-hash" and
"transmission-random-salt", that together are my solution to the problem of
assigning a value to the daemon's "rpc-password" configuration setting.
Transmission clients seem to expect the user to supply a password in
plaintext in their "settings.json" file. At startup, the client generates a
random, eight-character salt value; hashes it and the password together; and
writes the result back to the settings file, after which the password
remains obscured. This obviously violates the functional nature of Guix, as
we don't expect services to be rewriting their own configuration files and
the use of a random salt value makes the process non-repeatable anyway.
I've documented in the manual how a user can use these two procedures to
create a suitable value for "rpc-password" that remains stable across system
reconfigurations, but perhaps you know of a better (or more conventional)
approach.
- I've added a custom "stop" procedure to the Shepherd service that gives the
daemon time to shut down before eventually killing its process. This is
necessary since the daemon performs some housekeeping and sends a final
update to BitTorrent trackers before it exits, which can take several
seconds or more; without this code, restarting the service usually fails as
the new daemon process finds the old one is still running and attached to
the port used for peer connections.
Again, the approach I've used to handle this seems reasonable to me but
perhaps you know of something better.
--
Simon South
simon@simonsouth.net
Simon South (1):
services: Add transmission-daemon service.
doc/guix.texi | 799 +++++++++++++++++++++++++++++++++
gnu/local.mk | 1 +
gnu/services/file-sharing.scm | 806 ++++++++++++++++++++++++++++++++++
3 files changed, 1606 insertions(+)
create mode 100644 gnu/services/file-sharing.scm
--
2.28.0
next reply other threads:[~2020-11-04 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 12:37 Simon South [this message]
2020-11-04 12:40 ` [bug#44435] [PATCH 1/1] services: Add transmission-daemon service Simon South
2020-11-07 14:12 ` Simon South
2020-11-08 18:06 ` [bug#44435] [PATCH v2 0/1] services: Add Transmission Daemon Simon South
2020-11-08 18:06 ` [bug#44435] [PATCH v2 1/1] services: Add transmission-daemon service Simon South
2020-11-18 22:39 ` [bug#44435] [PATCH v2 0/1] services: Add Transmission Daemon Ludovic Courtès
2020-11-19 0:35 ` Simon South
2020-12-05 15:27 ` [bug#44435] [PATCH v3 " Simon South
2020-12-05 15:27 ` [bug#44435] [PATCH v3 1/1] services: Add transmission-daemon service Simon South
2021-02-12 7:15 ` bug#44435: [PATCH v3 0/1] services: Add Transmission Daemon 宋文武
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1604429058.git.simon@simonsouth.net \
--to=simon@simonsouth.net \
--cc=44435@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).