Alexander Dahl
338dfc7410
curl only logs its own errors to stderr with the given options (--silent
--show-error). Requests answered by the remote webserver, regardless of
HTTP status code, go to stdout. So in case of an unsuccesful update
with some error condition we could not see that before. Redirect those
to debug log, because it's still quite noisy otherwise.
This adds 288 log messages per day and service to the debug log,
accounting to max. 30k per day and service, and thus should not hurt.
desec log output is only the word "good" in case of success.
dd24 full output would be this, and is thus reduced to the relevant
lines merged in one line:
[RESPONSE]
code = 200
description = Command completed successfully
runtime = 0.067
queuetime = 0
EOF
Sample journald entry:
Feb 27 12:48:15 pottwal dd24[519651]: code = 200,description = Command completed successfully
6 lines
431 B
Django/Jinja
6 lines
431 B
Django/Jinja
# /etc/cron.d/dd24-dyndns: Cron call to renew DynDNS entry
|
|
|
|
SHELL=/bin/bash
|
|
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
|
|
|
|
*/5 * * * * root curl --silent --show-error "https://dynamicdns.key-systems.net/update.php?hostname={{dyndns_domain}}&password={{dyndns_password}}&ip={{dyndns_ip}}" > >(grep 'code\|description' | paste -d',' - - | logger -p user.debug -t dd24) 2> >(/usr/bin/logger -p user.error -t dd24)
|