Perhaps not, but your "solution" isn't helpful either. UPS isn't an option. Which is why I'm asking the question.
Torrents in ERROR state after crash with mergerfs
Re: Torrents in ERROR state after crash with mergerfs
My solution is the only solution to sudden power failure.
Like it or not...
Like it or not...
Re: Torrents in ERROR state after crash with mergerfs
There's no reason old torrents that aren't actively being downloaded should go into an error state. Crashes happen. There must be a way to turn off whatever is causing the error or mitigate it somehow. Again, I'd like a configuration based solution.
Re: Torrents in ERROR state after crash with mergerfs
The state of all torrents are saved to the same file. Age of the torrent is irrelevant. The file and overall state is corrupted. Because of power failure.
torrents.state and torrents.fastresume
torrents.state and torrents.fastresume