@ZimbiX I think that's going to be a problem as long as we CrashPlan continues to take their auto-upgrade approach. I think the general approach to counteract it today is:
- Clean out the upgrade packages and logs to get filesystem capacity back
- Upgrade to the latest package from AUR
- Start your backups again
#2 has been much more easy and reliable since the AUR package has been staying up-to-date since aaronm-cloudtek took over as the maintainer.
If this isn't good enough, you could always write and run a script that monitors whether it's trying to auto-apply a new upgrade and if so, stop the service before it downloads upgrade packages indefinitely until it files your filesystem. Then you could intervene with the new AUR package upgrade a little more easily.
Pinned Comments
achilleas commented on 2024-08-17 10:48 (UTC) (edited on 2024-08-17 10:49 (UTC) by achilleas)
I'm going to be disowning this package soon. I'm moving away from crashplan and have no interest in maintaining this package, and dealing with usage issues, when I wont be using it.
I'll keep it up to date during the coming months as needed, but if no one else shows up, I plan to disown it at the end of October.
SmashedSqwurl commented on 2018-12-19 15:10 (UTC) (edited on 2018-12-19 15:14 (UTC) by SmashedSqwurl)
@gadicc, I added some pacman hooks to handle setting/unsetting the immutable flag:
Sets immutable flag after install/upgrade:
Unsets immutable flag before upgrade/remove: