Rtorrent: Difference between revisions

(4 intermediate revisions by the same user not shown)

Line 2:

=== Integration with flood-js via UNIX sockets ===

rtorrent can open a socket which other software can use to interface with. No unprotected RPC socket of rtorrent is required with this setup and it therefore provides a higher security standard<syntaxhighlight lang="nix">

rtorrent can open a socket which other software can use to interface with. No unprotected RPC socket of rtorrent is required with this setup and it therefore provides a higher security standard.

{ config, lib, pkgs, ... }:

Line 13:

Line 15:

enable = true;

port = peer-port;

package = pkgs.~~jesec-~~rtorrent; # ~~currently~~ (~~2024~~-12-30) rtorrent ~~0.15.0~~ in nixpkgs ~~unstable is incompatible with flood, this is why a fork is used~~

package = pkgs.rtorrent; # (2025-07-28) upstream develop of rtorrent continued, jesec-rtorrent does not build in nixpkgs

openFirewall = true;

};

# If you have lots of torrents in the seed you may see rtorrent stack-trace with "too many open files"

# to increase the limit of open files use:

systemd.services.rtorrent.serviceConfig.LimitNOFILE = 16384;

services.flood = {

enable = true;

Line 26:

Line 32:

systemd.services.flood.serviceConfig.SupplementaryGroups = [ config.services.rtorrent.group ];

}

</syntaxhighlight>

</syntaxhighlight>Sample configuration is to be put into '''rtorrent.nix''' and imported in your '''configuration.nix''' via:

{

imports = [ ./rtorrent.nix ];

}

After performing '''nixos-rebuild switch''' on port http://localhost:8112 the flood service should run.

[[Category:Server]]

@@ Line 2: / Line 2: @@
 === Integration with flood-js via UNIX sockets ===
-rtorrent can open a socket which other software can use to interface with. No unprotected RPC socket of rtorrent is required with this setup and it therefore provides a higher security standard<syntaxhighlight lang="nix">
+rtorrent can open a socket which other software can use to interface with. No unprotected RPC socket of rtorrent is required with this setup and it therefore provides a higher security standard.
+<syntaxhighlight lang="nix">
 { config, lib, pkgs, ... }:
@@ Line 13: / Line 15: @@
      enable = true;
      port = peer-port;
-     package = pkgs.jesec-rtorrent; # currently (2024-12-30) rtorrent 0.15.0 in nixpkgs unstable is incompatible with flood, this is why a fork is used
+     package = pkgs.rtorrent; # (2025-07-28) upstream develop of rtorrent continued, jesec-rtorrent does not build in nixpkgs
      openFirewall = true;
    };
+  # If you have lots of torrents in the seed you may see rtorrent stack-trace with "too many open files"
+  # to increase the limit of open files use:
+  systemd.services.rtorrent.serviceConfig.LimitNOFILE = 16384;
    services.flood = {
      enable = true;
@@ Line 26: / Line 32: @@
    systemd.services.flood.serviceConfig.SupplementaryGroups = [ config.services.rtorrent.group ];
 }
-</syntaxhighlight>
+</syntaxhighlight>Sample configuration is to be put into '''rtorrent.nix''' and imported in your '''configuration.nix''' via:
+ {
+   imports = [ ./rtorrent.nix ];
+ }
+After performing '''nixos-rebuild switch''' on port http://localhost:8112 the flood service should run.
+[[Category:Server]]