|
From: SourceForge.net <no...@so...> - 2009-08-31 22:25:16
|
Feature Requests item #2451138, was opened at 2008-12-19 14:34 Message generated for change (Comment added) made by ziesemer You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2451138&group_id=116817 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Priority: 5 Private: No Submitted By: Mark Ziesemer (ziesemer) Assigned to: Nobody/Anonymous (nobody) Summary: Better support / timing for on-demand updates Initial Comment: I am unfortunately stuck with wireless, cellular Internet access over PPP. It is not very reliable, and it reconnects frequently, each time receiving a new IP address. I already have my system configured to call ddclient from my /etc/ppp/ip-up.d/ . DynDNS and other providers require that updates be at least 5 minutes apart. Consider the situation where I just got reconnected, and a successful update was performed. Between 0-5 minutes later, I'm reconnected again. ddclient is unable to update the IP with DynDns, either because it properly refrains from updating more than once within the 5 minute period, or because it receives a similar error back from DynDns - I've not yet looked into which is happening. Regardless, my IP is then not updated until the next time ddclient is called, probably due to the next reconnection event, which could leave me guessing at my next IP for the next several minutes, hours, or more. The alternative is to just use the daemon mode. However, I'd much rather prefer the event-based approach, which requires one less process to remain running at all times. Additionally, running daemon mode can be considered slower than the interface hooks. If my previous update was several hours ago, and a reconnection happens just seconds into a 5-minute daemon period, it could be 4+ minutes until the IP is updated, even though an immediate update would be valid. What I'd recommend is a "follow-up" option to the non-daemon mode. This would allow for ddclient to only run when necessary. If an update is requested before the minimum required time has elapsed, it could then spawn a new process that would sleep and update as soon as allowed - taking care to have this process canceled if there is yet another reconnection event during that time. ---------------------------------------------------------------------- Comment By: Mark Ziesemer (ziesemer) Date: 2009-08-31 17:25 Message: See bug # 2451365 instead... ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-12-20 07:12 Message: Please use the help forum to discuss such situations. You can start ddclient in deamon mode and send a HUP signal to force a renew. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2451138&group_id=116817 |
