Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

is there anyway to ignore the cache? #177

Closed
imthenachoman opened this issue Oct 3, 2017 · 4 comments
Closed

is there anyway to ignore the cache? #177

imthenachoman opened this issue Oct 3, 2017 · 4 comments

Comments

@imthenachoman
Copy link

Is there anyway to have inadyn ignore the cache? For example, say it sets the IP of my noip account to 1.2.3.4 and then I go to noip and change the IP to 2.3.4.5. My IP is still 1.2.3.4 so it should force update my noip IP. Right now it won't because inadyn has 1.2.3.4 in the cache and since my IP hasn't changed it doesn't bother doing an update.

@ysc3839
Copy link
Contributor

ysc3839 commented Oct 3, 2017

killall -SIGUSR1 inadyn

@imthenachoman
Copy link
Author

I mean when it is in daemon mode. Like it should always ignore the cache and always force an update, regardless if the machine's web/public IP did not change.

@troglobit
Copy link
Owner

The whole point of the cache is to prevent Inadyn from updating when there has been no change -- the reason for this is that most (possibly even all?) DDNS providers lock your account if there are too frequent or unnecessary updates.

If you really want to play with fire, check out the global forced-update = SEC setting, setting it to the same or less than the update interval should be sufficient. Or set up an inotify/dnotify/cronjob script to remove the cache file(s), for a more granular per-provider set up.

@imthenachoman
Copy link
Author

Understood. You are right. When I think about it there is no reason to force update if the public IP hasn't changed. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants