[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Grant Sewell wrote:
AFAIK, all daemon mode does is put ddclient in a loop so it checks the IP every minute so I don't think you should have a problem running in daemon mode. I just run with the default options. The only thing I have changed is that I get the IP from my router not from the dyndns web page. That way it doesn't have to go out to the internet every minute. I don't use the force or retry options at all, I think the default is to force an update every 14 days but I haven't checked that.I had the above two lines uncommented. I chose not to run in daemon mode because there'd be nothing to actually trigger an update, so I had to go for cron mode. The problem I have is that, as I see it (bear in mind that I have no real experience with dynamic dns) the 2nd entry is triggered every hour by cron but it won't actually do anything unless the other (monthly) cron job had previously failed. So, basically once a month my ddclient would forcibly try to update my dyndns entry and then if it failed, try again ever hour. This would not be helpful for me because I can't guarantee when my IP would change. If I need to change a setting on my primary router (the non-IPCop box) then it'd need to be rebooted, but my IPCop box wouldn't pick up this reboot and possibly not actually change my dyndns entry for upto a month! And obviously, if my IP changes then I won't know what it is in order to ssh into my IPCop box from College and do a manual ddclient update.
Hope this helps.
Pete
Or am I reading the whole thing wrong?
Cheers.
Grant.
-- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html