transmission-daemon
Run Transmission BitTorrent client in the background
TLDR
Start a headless transmission session
Start and watch a specific directory for new torrents
Dump daemon settings in JSON format
Start with specific settings for the web interface
SYNOPSIS
transmission-daemon [options]
PARAMETERS
-a
Set the bind address.
-b
Set the blocklist URL.
-d
Set the download directory.
-e
Set the log file.
-f
Foreground mode (don't daemonize).
-g
Set the configuration directory.
-o
Display the configuration directory.
-t
Enable TR_CLIENT_TEST.
-V
Show version number and exit.
-v [level]
Set the log level.
-w
Set the username.
-x
Set the password.
DESCRIPTION
transmission-daemon is a headless BitTorrent client ideal for servers, embedded systems, and resource-constrained environments. It runs as a background process, controlled through a web interface (transmission-web), a command-line interface (transmission-remote), or other third-party applications.
It handles downloading and seeding torrents without requiring a graphical user interface. Configuration is typically done through a settings file (settings.json) or via the web interface. The daemon monitors specified directories for .torrent files, automatically adding them to the download queue. It efficiently manages bandwidth, peers, and file transfers, making it a popular choice for users who want a dedicated, always-on torrent client without the overhead of a full desktop application.
This provides hands-off and very minimal way of running a torrent client, and usually is much more practical on servers or embedded systems where a full GUI is not desirable.
CONFIGURATION FILE
The configuration file (settings.json) allows for persistent configuration of the daemon, including download locations, bandwidth limits, peer settings, and other parameters. Editing this file directly requires stopping the daemon first to prevent data corruption.
WEB INTERFACE
The web interface (transmission-web) provides a user-friendly way to manage torrents, view statistics, and configure the daemon. It is typically accessible through a web browser at a specified port (default is 9091).
SEE ALSO
transmission-remote(1), transmission-cli(1), transmission-gtk(1)
