Borg Backup Server

Bug fixes

• Windows: stale borg cache lock not cleared after cancel (#298). When a backup was cancelled on Windows, the local cache lock.exclusive file was left behind, blocking the next backup with a lock timeout. The cleanup routine was checking the legacy %LOCALAPPDATA%\borg\Cache path, but modern borg uses ~/.cache/borg/ on Windows too — which for a service running as SYSTEM resolves to C:\WINDOWS\system32\config\systemprofile\.cache\borg\. The agent now sweeps all three locations (BORG_CACHE_DIR if set, ~/.cache/borg, and the legacy path) before every backup.

• Shell-script plugin: better error messages (#297). When a pre/post script can't run, the agent used to log just "not found" or "not executable", which hid the most common cause: the agent user couldn't traverse a parent directory, or ownership didn't match. The error now distinguishes between missing parent dir, unreadable parent, missing file (with sibling listing for typos), wrong perms, and not executable — each with the file's perms, owner, and the agent's effective uid so the cause is obvious from the log alone.