Closed rugk closed 1 year ago
I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/ddclient/v3.9.1-pkg-89af875f-pr-52/index.html https://ci-tests.linuxserver.io/lspipepr/ddclient/v3.9.1-pkg-89af875f-pr-52/shellcheck-result.xml
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
…
I don't think the term template
really fits here, as it is a default file, that path is also not meant to be touched by the user. /config/ddclient.conf
is the file the user is supposed to alter.
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/ddclient/v3.9.1-pkg-fba6e7d8-pr-52/index.html https://ci-tests.linuxserver.io/lspipepr/ddclient/v3.9.1-pkg-fba6e7d8-pr-52/shellcheck-result.xml
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This pull request is locked due to inactivity
Description:
This Readme change aims to fix the problem described below by explicitly hinting at that file and shortly describing what happens, if you do not use/include the
daemon=300
directive there.Benefits of this PR and context:
I had the issue that if you include a config file the
daemon=300
directive from the default ddclient config is not applied and you need it in your manual configuration file. Otherwise, ddclient pings the server way too fast, whcih can lead to rate limits etc.How Has This Been Tested?
Locally by adjusting the config file.
Source / References:
https://talk.desec.io/t/running-into-429-too-many-requests-for-https-checkipv4-dedyn-io/284?u=rugk