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.
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).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bortzmeyer on GitHub (Dec 2, 2017).
By default,
dehydrated --cronis very talkative: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.
@bortzmeyer commented on GitHub (Dec 2, 2017):
It was apparently already requested in #47 and #331 but never solved.
@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).