starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-01-11 22:30:44 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

Too talkative #265

New Issue
Closed
opened 2025-12-29 01:20:35 +01:00 by adam · 2 comments
adam commented 2025-12-29 01:20:35 +01:00
Owner
Copy Link

Originally created by @bortzmeyer on GitHub (Dec 2, 2017).

By default, dehydrated --cron is very talkative:

Processing dns.bortzmeyer.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jan 23 05:25:11 2018 GMT Certificate will not expire (Longer than 30 days). Skipping renew!

This triggers an email from cron, whcih is useless.

I find no option to make dehydrated more quiet. Redirecting to /dev/null is of course not an option, since I still want to know when the certificate is renewed.

Originally created by @bortzmeyer on GitHub (Dec 2, 2017). By default, `dehydrated --cron` is very talkative: ``` Processing dns.bortzmeyer.org + Checking domain name(s) of existing cert... unchanged. + Checking expire date of existing cert... + Valid till Jan 23 05:25:11 2018 GMT Certificate will not expire (Longer than 30 days). Skipping renew! ``` This triggers an email from cron, whcih is useless. I find no option to make dehydrated more quiet. Redirecting to /dev/null is of course not an option, since I still want to know when the certificate is renewed.
adam closed this issue 2025-12-29 01:20:35 +01:00
adam commented 2025-12-29 01:20:37 +01:00
Author
Owner
Copy Link

@bortzmeyer commented on GitHub (Dec 2, 2017):

It was apparently already requested in #47 and #331 but never solved.

@bortzmeyer commented on GitHub (Dec 2, 2017): It was apparently already requested in #47 and #331 but never solved.
adam commented 2025-12-29 01:20:37 +01:00
Author
Owner
Copy Link

@lukas2511 commented on GitHub (Dec 5, 2017):

This will stay this way unless somebody puts work into a logging system.
I personally really really like verbose output and if you want to run it in a cronjob you should have a look at the suggestions from those past tickets (use a special "wrapper" tool and hooks).

@lukas2511 commented on GitHub (Dec 5, 2017): This will stay this way unless somebody puts work into a logging system. I personally really really like verbose output and if you want to run it in a cronjob you should have a look at the suggestions from those past tickets (use a special "wrapper" tool and hooks).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complicated
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 suggestions wanted
testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#265
Delete Branch "%!s()"

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?