borgmatic-collective/borgmatic
10
71
Fork 43
Code Issues 48 Pull Requests 6 Actions 1 Packages Releases 153 Activity

Reduce console output in sample crontab/systemd service files. #379

Merged
witten merged 1 commits from :cron-systemd-verbosity into master 2021-06-23 17:32:48 +00:00
Conversation 3 Commits 1 Files Changed 2 +2 -2
jefferyto commented 2020-12-08 09:19:49 +00:00
Contributor
Copy Link

As borgmatic will log to syslog in the sample crontab/systemd service files, this makes console output redundant. (cron will mail any console output to the root user; systemd will log any console output to syslog.)

This adds --verbosity -1 to both files to reduce console output to the minimum.

As borgmatic will log to syslog in the sample crontab/systemd service files, this makes console output redundant. (cron will mail any console output to the root user; systemd will log any console output to syslog.) This adds `--verbosity -1` to both files to reduce console output to the minimum.
jefferyto commented 2020-12-08 09:25:57 +00:00
Author
Contributor
Copy Link

Please note that I have only tested (and am using this change) in the systemd service file. I haven't personally tested the crontab change but I don't see how it can have any negative effects.

Please note that I have only tested (and am using this change) in the systemd service file. I haven't personally tested the crontab change but I don't see how it can have any negative effects.
jefferyto force-pushed cron-systemd-verbosity from 5890068e3e to 831878ed32 2020-12-08 09:29:24 +00:00 Compare
jefferyto changed title from Reduce console output in sample cron/systemd service files. to Reduce console output in sample crontab/systemd service files. 2020-12-08 09:29:38 +00:00
palto42 commented 2020-12-08 18:42:44 +00:00
Contributor
Copy Link

My solution for systemd was to set StandardOutput=null in the service configuration which bins any console output.

My solution for systemd was to set `StandardOutput=null` in the service configuration which bins any console output.
jefferyto force-pushed cron-systemd-verbosity from 831878ed32 to 01c9065a8c 2021-02-09 08:30:09 +00:00 Compare
jefferyto force-pushed cron-systemd-verbosity from 01c9065a8c to d1c403999f 2021-04-12 17:41:44 +00:00 Compare
witten commented 2021-06-23 17:32:07 +00:00
Owner
Copy Link

Sorry for the long delay here! This looks like a reasonable change to me. Thank you.

Sorry for the long delay here! This looks like a reasonable change to me. Thank you.
witten merged commit bc2e611a74 into master 2021-06-23 17:32:48 +00:00
jefferyto deleted branch cron-systemd-verbosity 2021-10-07 05:19:00 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
witten
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#379
Delete Branch ":cron-systemd-verbosity"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?