borgmatic-collective
/
borgmatic
12
47
Fork 45
Code Issues 67 Pull Requests Packages Releases 104 Activity

Labels Milestones

Do not inhibit idle in borgmatic.service #589

Merged
witten merged 1 commits from LaserEyess/borgmatic:service_fix into master 6 months ago
Conversation 1 Commits 1 Files Changed 1
LaserEyess commented 6 months ago

When backing up a machine with a monitor using logind to control idle
timeout and things like DPMS, borgmatic can block the screen from
turning on/off with systemd-inhibit. This is because by default
systemd-inhibit will block "idle:sleep:shutdown". Borgmatic does not
need to care about idle, only about suspend and shutdown. So, add an
explicit --what flag for what borgmatic should inhibit.

For more information see systemd-inhibit(1).

When backing up a machine with a monitor using logind to control idle timeout and things like DPMS, borgmatic can block the screen from turning on/off with systemd-inhibit. This is because by default systemd-inhibit will block "idle:sleep:shutdown". Borgmatic does not need to care about idle, only about suspend and shutdown. So, add an explicit `--what` flag for what borgmatic should inhibit. For more information see systemd-inhibit(1).
witten commented 6 months ago
Owner

Awesome! Thank you for taking the time to diagnose and fix this.

Awesome! Thank you for taking the time to diagnose and fix this.
witten merged commit c969c822ee into master 6 months ago
The pull request has been merged as c969c822ee.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b LaserEyess-service_fix master
git pull service_fix

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff LaserEyess-service_fix
git push origin master
Sign in to join this conversation.
Reviewers
Request review
No reviewers
Labels
Apply labels
Clear labels   
bug
   
data loss
   
design finalized
   
good first issue
   
question / support
   
security
   
waiting for response
No Label
bug
data loss
design finalized
good first issue
question / support
security
waiting for response
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#589
Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch 'LaserEyess/borgmatic:service_fix'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes