I’m running an old version of Transmission (2.42) on an ancient Linux BusyBox which has worked just fine for years.
Recently I had a stubborn segment of a file that caused Transmission to freeze and lock up the system entirely. I couldn’t even issue a reboot command. By isolating (preventing download of) the segment it was easy to bypass the issue but still – what could be the reason for this? A bad file, a bad torrent, someone trying to exploit this old version? Any ideas?
Anyway, I have opkg installed and have the option to upgrade to 3.00:
transmission-cli - 3.00-1 - lightweight BitTorrent client (command line interface)
transmission-common - 3.00-1 - lightweight BitTorrent client (common files)
transmission-daemon - 3.00-1 - lightweight BitTorrent client (daemon)
I believe the one I need is the daemon.
Will the opkg install completely overwrite (upgrade) the old version or will it install as a separate program in another location alongside the native program (presumably in /bin)?
My understanding is that the install will be in /opt but that the old service will be overwritten with the new one giving me uninterupted access to Transmission via clutch start-stop-save and the service listening on port 9091 (for remote access).
How do I set where the settings.json etc. should be located (old version puts them in a hidden folder at /share/.transmission).
Will I be able to downgrade again using opkg if anything goes wrong (I don’t have access to the install files of Transmission 2.42 – only a backup of the entire system)?
I’m not super familiar with the workings of Linux so please bear with me. Any suggestions and ideas much welcome.
