Opened 8 years ago
Last modified 7 years ago
#5654 new Bug
transmission-daemon does not exit if configuration directory does not exist or is not accessible
Reported by: | chris_u | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | None Set |
Component: | Daemon | Version: | 2.52 |
Severity: | Normal | Keywords: | configuration, daemon, exit |
Cc: |
Description
If the configuration directory does not exist or is not accessible (permissions), the transmission-daemon runs anyway. A default configuration is used that looks like the stock settings.json. The web interface at <host>:9091 can be accessed. I think the daemon should fail and exit if it has no access to the given configuration.
Tried with transmission-daemon versions 2.52, 2.77, r14255 on Linux (Ubuntu, Raspbian).
Example:
$ sudo -u debian-transmission /usr/bin/transmission-daemon -g /var/lib/bogus -f -a '*'
Output:
[10:12:39.441] Couldn't create "/var/lib/bogus": Permission denied (utils.c:571) [10:12:39.443] Couldn't create "/var/lib/bogus": Permission denied (utils.c:571) [10:12:39.444] Couldn't create "/var/lib/bogus": Permission denied (utils.c:571) [10:12:39.445] Transmission 2.52 (13304) started (session.c:718) [10:12:39.446] RPC Server Adding address to whitelist: * (rpc-server.c:803) [10:12:39.447] RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:997) [10:12:39.448] RPC Server Whitelist enabled (rpc-server.c:1001) [10:12:39.450] DHT Generating new id (tr-dht.c:309) [10:12:39.450] Using settings from "/var/lib/bogus" (daemon.c:488) [10:12:39.450] Couldn't save temporary file "/var/lib/bogus/settings.json.tmp.nm9ymz": No such file or directory (bencode.c:1744) [10:12:39.451] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:72) ...
transmission-daemon runs, webinterface is accessible at <host>:9091.
Change History (2)
comment:1 Changed 7 years ago by mike.dld
- Component changed from Transmission to Daemon
comment:2 Changed 7 years ago by mike.dld
- Version changed from 2.82+ to 2.52
Note: See
TracTickets for help on using
tickets.