LinuxCommandLibrary

deluged

Run Deluge BitTorrent daemon

TLDR

Start the Deluge daemon

$ deluged
copy

Start the Deluge daemon on a specific port
$ deluged [[-p|--port]] [port]
copy

Start the Deluge daemon using a specific configuration file
$ deluged [[-c|--config]] [path/to/configuration_file]
copy

Start the Deluge daemon and output the log to a file
$ deluged [[-l|--logfile]] [path/to/log_file]
copy

SYNOPSIS

deluged [-c config_dir] [-L loglevel] [-l logfile] [-i interface] [-p pidfile] [-P port] [-d] [-q] [-v] [--help]

PARAMETERS

-h, --help
    Display usage summary and exit

-v, --version
    Show Deluge version and exit

-c DIR, --config DIR
    Set configuration directory (default: ~/.config/deluge)

-L LEVEL, --loglevel LEVEL
    Log level: debug|info|warning|error|none

-l FILE, --logfile FILE
    Log to specified file instead of stdout

-i INTERFACE, --interface INTERFACE
    Bind to network interface/IP (default: all)

-p FILE, --pidfile FILE
    Write process ID to file

-P PORT, --port PORT
    Daemon listen port (default: 58846)

-d, --daemonize
    Fork and run as background daemon

-q, --quiet
    Suppress startup banner

--check-running
    Exit if daemon already running

--usage
    Print brief usage and exit

DESCRIPTION

deluged is the server-side daemon for the Deluge BitTorrent client, a free, open-source, cross-platform application written in Python using libtorrent as its backend. It runs silently in the background, managing torrent downloads, uploads, seeding, and peer interactions without a graphical interface. This modular design allows thin clients like Deluge's GTK UI, web interface (deluge-web), or console (deluge-console) to connect remotely over a JSON-RPC protocol, supporting usage across local or remote machines.

Key features include plugin support for extensions, bandwidth limits, scheduling, proxy settings, and encryption. Configuration files reside in a user-specified directory (default: ~/.config/deluge), with core.conf holding daemon settings like port and auth. Start it once with options for logging, interface binding, and daemonization, then control via clients. Ideal for headless servers or NAS devices, it's lightweight (minimal CPU/RAM) yet powerful for heavy torrenting.

Security note: Enable authentication and use firewalls, as it listens on TCP ports by default.

CAVEATS

Requires libtorrent-rasterbar library. Default password 'deluge' must be changed for security. Does not auto-start torrents; use clients. PID file prevents multiple instances but check manually if issues. Logs rotate poorly without external tools.

DEFAULT CONFIG FILES

core.conf: daemon settings (port, auth).
auth: 'username:password:remote_ip' format.
auth.private: local-only users.

STOPPING THE DAEMON

Kill via PID file: kill $(cat pidfile) or deluge-console 'shutdown' after connecting.

REMOTE ACCESS

Set allow_remote: true in core.conf. Clients connect via localhost:58846 or remote IP.

HISTORY

Deluge project started in 2006 by developers seeking a flexible GTK+ client. Client-server model with deluged added in v1.0 (2008) for remote control. Evolved to v2.x with Python 3, libtorrent 2.x support. Maintained by community on GitHub; widely used on Linux distros since 2010.

SEE ALSO

deluge(1), deluge-console(1), deluge-web(1), transmission-daemon(1), rtorrent(1)

Copied to clipboard