You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
The previous systemd service works great for starting/stoping cloud-torrent but when I stop it, cloud-torrent always overwrites the config file /home/nginx/Tools/cloud-torrent/cloud-torrent.json It doesn't matter if I edit the file before starting cloud-torrent, it always overwrites the config file on shutdown. It's like cloud-torrent has an in memory config file or a cached one which is written on disk (decerialized) on each shutdown.
IS there any way to avoid it or to fix the issue? Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've just installed cloud-torrent version through
Then I created the following systemd unit file, which works great for managing cloud-init as a service
[Unit]
Description=Cloud Torrent System Daemon
After=network.target
[Service]
Type=simple
User=nginx
Group=nginx
WorkingDirectory=/home/nginx/Tools/cloud-torrent/
ExecStart=/usr/local/bin/cloud-torrent -h 127.0.0.1 --config-path /home/nginx/Tools/cloud-torrent/cloud-torrent.json --title "Cloud Torrent" --log --auth "admin:changeme"
StandardOutput=append:/var/log/cloud-torrent.log
Restart=on-failure
RestartSec=3
[Install]
WantedBy=multi-user.target
The previous systemd service works great for starting/stoping cloud-torrent but when I stop it, cloud-torrent always overwrites the config file /home/nginx/Tools/cloud-torrent/cloud-torrent.json It doesn't matter if I edit the file before starting cloud-torrent, it always overwrites the config file on shutdown. It's like cloud-torrent has an in memory config file or a cached one which is written on disk (decerialized) on each shutdown.
IS there any way to avoid it or to fix the issue? Thanks!
The text was updated successfully, but these errors were encountered: