ddclient-forum Mailing List for ddclient (Page 5)
Brought to you by:
supersandro2000,
wimpunk
This list is closed, nobody may subscribe to it.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(25) |
Sep
(27) |
Oct
(37) |
Nov
(35) |
Dec
(14) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
|
Feb
(36) |
Mar
(14) |
Apr
(13) |
May
(23) |
Jun
(23) |
Jul
(10) |
Aug
|
Sep
(12) |
Oct
(7) |
Nov
(35) |
Dec
(23) |
2009 |
Jan
(19) |
Feb
(16) |
Mar
(15) |
Apr
(18) |
May
(8) |
Jun
(11) |
Jul
(5) |
Aug
(22) |
Sep
(4) |
Oct
(11) |
Nov
(4) |
Dec
(1) |
2010 |
Jan
(1) |
Feb
(2) |
Mar
(1) |
Apr
(1) |
May
(7) |
Jun
(12) |
Jul
(9) |
Aug
(2) |
Sep
(7) |
Oct
(5) |
Nov
|
Dec
(2) |
2011 |
Jan
|
Feb
(8) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
2012 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: SourceForge.net <no...@so...> - 2009-09-01 08:09:50
|
Patches item #1609799, was opened at 2006-12-06 05:09 Message generated for change (Comment added) made by scilence You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1609799&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: new services Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Erik Christiansson (scilence) Assigned to: Nobody/Anonymous (nobody) Summary: Support for LoopiaDNS Initial Comment: LoopiaDNS uses a subset of the DynDNS2 protocol. The address used for updating is http://dns.loopia.se/XDynDNSServer/XDynDNS.php The 'server' setting didn't help since the last part of the URL was hardcoded to /nic/update. The 'script' setting was added to fix this. Loopia also provides a web based IP lookup at http://dns.loopia.se/checkip/checkip.php that was added. Sample config: protocol=dyndns2, use=web, web=loopia, server=dns.loopia.se, script=/XDynDNSServer/XDynDNS.php, login=myaccount, password=mysecret, f.q.d.n ---------------------------------------------------------------------- >Comment By: Erik Christiansson (scilence) Date: 2009-09-01 10:09 Message: I've updated the patch to SVN version. It would be great to get this merged. I've been patching releases for three years now. ---------------------------------------------------------------------- Comment By: John Backstrand (sandos) Date: 2006-12-06 13:27 Message: Logged In: YES user_id=22211 Originator: NO This would be extremely useful. Please add this to ddclient, since Loopia is clearly the most common registrar for new .se domains. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1609799&group_id=116817 |
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 |
From: SourceForge.net <no...@so...> - 2009-08-22 20:39:13
|
Patches item #2842732, was opened at 2009-08-22 22:39 Message generated for change (Tracker Item Submitted) made by skangas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2842732&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: Open Resolution: None Priority: 5 Private: No Submitted By: Stefan Kangas (skangas) Assigned to: Nobody/Anonymous (nobody) Summary: ddclient.cache doesn't get IP if server doesn't echo it Initial Comment: Attached is a patch which fixes a bug which will appear in some cases where service providers give status responses not containing the client's IP address. Currently, ddclient relies on this behaviour and if the service provider gives a broken response it will lead to errors as detailed in the bug report in the Debian BTS (linked below). Here's a log from where I've reproduced this error with my own service provider: $ ./ddclient -debug -file ddclient.conf -cache ./ddclient.cache DEBUG: proxy = DEBUG: url = http://www.whatismyip.com/automation/n09230945.asp DEBUG: server = www.whatismyip.com DEBUG: get_ip: using web, http://www.whatismyip.com/automation/n09230945.asp reports 81.xx.xx.xx DEBUG: DEBUG: nic_dyndns2_update ------------------- DEBUG: proxy = DEBUG: url = http://xxxxx/nic/update?system=custom&hostname=xxxxx&myip=81.xx.xx.xx&wildcard=ON DEBUG: server = xxxxxx Use of uninitialized value $_[2] in sprintf at ./ddclient line 1550. SUCCESS: updating xxxxx: good: IP address set to $ cat ddclient.cache ## ddclient-3.8.0 ## last updated at Sat Aug 22 22:22:20 2009 (1250972540) atime=1250972540,backupmx=0,custom=1,host=xxxxxxx,ip=,mtime=1250972540,mx=,static=0,status=good,warned-min-error-interval=0,warned-min-interval=0,wildcard=1,wtime=0 xxxxxx http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528950 This patch is tested and verified working by myself. Please consider including this patch in ddclient. Regards, Stefan Kangas ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=2842732&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-18 10:17:36
|
Patches item #1893144, was opened at 2008-02-13 23:18 Message generated for change (Comment added) made by shmlchr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&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: Open Resolution: None Priority: 5 Private: No Submitted By: John Palkovic (drjohnny) Assigned to: wimpunk (wimpunk) Summary: Foreground patch Initial Comment: I am running ddclient as a dyndns.org client on a debian etch system. I had some problems with the startup script in the debian package. It was also out of date with no ssl support. I decided to patch ddclient to run under the control of runit (http://smarden.org/runit), a unix service supervisor akin to svscan (http://cr.yp.to/daemontools/svscan.html). I created the patch and have been running with it for a week with no issues to report. The patch adds a -foreground argument. When called with this argument, ddclient runs as a daemon but does not fork(). This is appropriate for use with runit or svscan (or launchd on a darwin system). There are changes to the daemon logic, so I would appreciate any comments. I will attach the patch with the upload button. -John Palkovic 13 Feb 2008 ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-18 12:17 Message: Seems that only the person who originated an artifact is able to post attachments. In another artifact that I have opened myself, I can add attachments easily. No problem, here we go: http://ddclient.pastebin.ca/1533623 Would be great if this made it into some future version; right now 3.8.0 works just fine for me though. Thanks for a great product and for still taking good care of it. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2009-08-18 07:44 Message: It's a little strange you can't attach a file but as a work around, could you send me the patch or post it to http://ddclient.pastbin.ca and put a link to it here. I'll attach it here and take a second look to apply it to ddclient official release. ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-17 22:37 Message: Well, seems I cannot attach anything here, so here goes the patch against 3.8.0: --- ddclient-3.8.0 2009-01-27 20:14:02.000000000 +0100 +++ ddclient+foreground-3.8.0 2009-08-17 22:27:32.000000000 +0200 @@ -307,6 +307,7 @@ my %variables = ( 'global-defaults' => { 'daemon' => setv(T_DELAY, 0, 0, 1, 0, interval('60s')), + 'foreground' => setv(T_BOOL, 0, 0, 1, 0, undef), 'file' => setv(T_FILE, 0, 0, 1, "$etc$program.conf", undef), 'cache' => setv(T_FILE, 0, 0, 1, "$cachedir$program.cache", undef), 'pid' => setv(T_FILE, 0, 0, 1, "", undef), @@ -535,6 +536,7 @@ "usage: ${program} [options]", "options are:", [ "daemon", "=s", "-daemon delay : run as a daemon, specify delay as an interval." ], ++ [ "foreground", "!", "-foreground : do not fork" ], [ "proxy", "=s", "-proxy host : use 'host' as the HTTP proxy" ], [ "server", "=s", "-server host : update DNS information on 'host'" ], [ "protocol", "=s", "-protocol type : update protocol used" ], @@ -623,7 +625,10 @@ $SIG{'HUP'} = sub { $caught_hup = 1; }; $SIG{'TERM'} = sub { $caught_term = 1; }; $SIG{'KILL'} = sub { $caught_kill = 1; }; -if (opt('daemon') && !opt('force')) { +# don't fork() if foreground or force is on +if (opt('foreground') || opt('force')) { + ; +} elsif (opt('daemon')) { $SIG{'CHLD'} = 'IGNORE'; my $pid = fork; if ($pid < 0) { @@ -633,12 +638,15 @@ exit 0; } $SIG{'CHLD'} = 'DEFAULT'; - $opt{'syslog'} = 1; open(STDOUT, ">/dev/null"); open(STDERR, ">/dev/null"); open(STDIN, "</dev/null"); +} +# write out the pid file if we're daemon'ized +if(opt('daemon')) { write_pid(); + $opt{'syslog'} = 1; } umask 077; ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-17 22:30 Message: Thanks a lot drjohnny. I'm using your patch on Mac OS X 10.5.8 with launchd. I have attached the same patch applied against 3.8.0. All credit goes to drjohnny, mistakes are mine. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-18 09:28 Message: Logged In: YES user_id=722282 Originator: NO You're correct, I've made a mistake. Your patch could also be useful for debugging so I think I'll take closer look and maybe it will get included in the next release of ddclient. ---------------------------------------------------------------------- Comment By: John Palkovic (drjohnny) Date: 2008-02-14 01:02 Message: Logged In: YES user_id=985118 Originator: YES You are mistaken. fork() cannot be called, nor can exit() be reached to run properly under the control of runit or svscan. I want behavior like (apache2) httpd -DFOREGROUND or cron -f. ddclient -daemon=0 is not a daemon, it exits quickly on my debian etch box: # date Wed Feb 13 17:45:42 CST 2008 # time ddclient -daemon=0 -file /etc/ddclient.conf real 0m0.392s user 0m0.280s sys 0m0.036s This behavior is obvious if one glances at the while() statement on line 655 of 3.7.3. I want the program to loop in the do/while beginning on line 598 of version 3.7.3 without ever having called fork(). It should not exit() unless forced to by a signal or a restart. It must not call fork(). Do you understand? I don't think this functionality is available in the stock 3.7.3. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-14 00:00 Message: Logged In: YES user_id=722282 Originator: NO As far as I can see, you don't need a patch, you just need the daemon=0 option. I'm also wondering why you had some startup problems with the debian package. I didn't got any report about that from other people. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-18 05:44:35
|
Patches item #1893144, was opened at 2008-02-13 22:18 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&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: Open Resolution: None Priority: 5 Private: No Submitted By: John Palkovic (drjohnny) Assigned to: wimpunk (wimpunk) Summary: Foreground patch Initial Comment: I am running ddclient as a dyndns.org client on a debian etch system. I had some problems with the startup script in the debian package. It was also out of date with no ssl support. I decided to patch ddclient to run under the control of runit (http://smarden.org/runit), a unix service supervisor akin to svscan (http://cr.yp.to/daemontools/svscan.html). I created the patch and have been running with it for a week with no issues to report. The patch adds a -foreground argument. When called with this argument, ddclient runs as a daemon but does not fork(). This is appropriate for use with runit or svscan (or launchd on a darwin system). There are changes to the daemon logic, so I would appreciate any comments. I will attach the patch with the upload button. -John Palkovic 13 Feb 2008 ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2009-08-18 05:44 Message: It's a little strange you can't attach a file but as a work around, could you send me the patch or post it to http://ddclient.pastbin.ca and put a link to it here. I'll attach it here and take a second look to apply it to ddclient official release. ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-17 20:37 Message: Well, seems I cannot attach anything here, so here goes the patch against 3.8.0: --- ddclient-3.8.0 2009-01-27 20:14:02.000000000 +0100 +++ ddclient+foreground-3.8.0 2009-08-17 22:27:32.000000000 +0200 @@ -307,6 +307,7 @@ my %variables = ( 'global-defaults' => { 'daemon' => setv(T_DELAY, 0, 0, 1, 0, interval('60s')), + 'foreground' => setv(T_BOOL, 0, 0, 1, 0, undef), 'file' => setv(T_FILE, 0, 0, 1, "$etc$program.conf", undef), 'cache' => setv(T_FILE, 0, 0, 1, "$cachedir$program.cache", undef), 'pid' => setv(T_FILE, 0, 0, 1, "", undef), @@ -535,6 +536,7 @@ "usage: ${program} [options]", "options are:", [ "daemon", "=s", "-daemon delay : run as a daemon, specify delay as an interval." ], ++ [ "foreground", "!", "-foreground : do not fork" ], [ "proxy", "=s", "-proxy host : use 'host' as the HTTP proxy" ], [ "server", "=s", "-server host : update DNS information on 'host'" ], [ "protocol", "=s", "-protocol type : update protocol used" ], @@ -623,7 +625,10 @@ $SIG{'HUP'} = sub { $caught_hup = 1; }; $SIG{'TERM'} = sub { $caught_term = 1; }; $SIG{'KILL'} = sub { $caught_kill = 1; }; -if (opt('daemon') && !opt('force')) { +# don't fork() if foreground or force is on +if (opt('foreground') || opt('force')) { + ; +} elsif (opt('daemon')) { $SIG{'CHLD'} = 'IGNORE'; my $pid = fork; if ($pid < 0) { @@ -633,12 +638,15 @@ exit 0; } $SIG{'CHLD'} = 'DEFAULT'; - $opt{'syslog'} = 1; open(STDOUT, ">/dev/null"); open(STDERR, ">/dev/null"); open(STDIN, "</dev/null"); +} +# write out the pid file if we're daemon'ized +if(opt('daemon')) { write_pid(); + $opt{'syslog'} = 1; } umask 077; ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-17 20:30 Message: Thanks a lot drjohnny. I'm using your patch on Mac OS X 10.5.8 with launchd. I have attached the same patch applied against 3.8.0. All credit goes to drjohnny, mistakes are mine. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-18 08:28 Message: Logged In: YES user_id=722282 Originator: NO You're correct, I've made a mistake. Your patch could also be useful for debugging so I think I'll take closer look and maybe it will get included in the next release of ddclient. ---------------------------------------------------------------------- Comment By: John Palkovic (drjohnny) Date: 2008-02-14 00:02 Message: Logged In: YES user_id=985118 Originator: YES You are mistaken. fork() cannot be called, nor can exit() be reached to run properly under the control of runit or svscan. I want behavior like (apache2) httpd -DFOREGROUND or cron -f. ddclient -daemon=0 is not a daemon, it exits quickly on my debian etch box: # date Wed Feb 13 17:45:42 CST 2008 # time ddclient -daemon=0 -file /etc/ddclient.conf real 0m0.392s user 0m0.280s sys 0m0.036s This behavior is obvious if one glances at the while() statement on line 655 of 3.7.3. I want the program to loop in the do/while beginning on line 598 of version 3.7.3 without ever having called fork(). It should not exit() unless forced to by a signal or a restart. It must not call fork(). Do you understand? I don't think this functionality is available in the stock 3.7.3. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-13 23:00 Message: Logged In: YES user_id=722282 Originator: NO As far as I can see, you don't need a patch, you just need the daemon=0 option. I'm also wondering why you had some startup problems with the debian package. I didn't got any report about that from other people. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-17 20:37:24
|
Patches item #1893144, was opened at 2008-02-13 23:18 Message generated for change (Comment added) made by shmlchr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&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: Open Resolution: None Priority: 5 Private: No Submitted By: John Palkovic (drjohnny) Assigned to: wimpunk (wimpunk) Summary: Foreground patch Initial Comment: I am running ddclient as a dyndns.org client on a debian etch system. I had some problems with the startup script in the debian package. It was also out of date with no ssl support. I decided to patch ddclient to run under the control of runit (http://smarden.org/runit), a unix service supervisor akin to svscan (http://cr.yp.to/daemontools/svscan.html). I created the patch and have been running with it for a week with no issues to report. The patch adds a -foreground argument. When called with this argument, ddclient runs as a daemon but does not fork(). This is appropriate for use with runit or svscan (or launchd on a darwin system). There are changes to the daemon logic, so I would appreciate any comments. I will attach the patch with the upload button. -John Palkovic 13 Feb 2008 ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-17 22:37 Message: Well, seems I cannot attach anything here, so here goes the patch against 3.8.0: --- ddclient-3.8.0 2009-01-27 20:14:02.000000000 +0100 +++ ddclient+foreground-3.8.0 2009-08-17 22:27:32.000000000 +0200 @@ -307,6 +307,7 @@ my %variables = ( 'global-defaults' => { 'daemon' => setv(T_DELAY, 0, 0, 1, 0, interval('60s')), + 'foreground' => setv(T_BOOL, 0, 0, 1, 0, undef), 'file' => setv(T_FILE, 0, 0, 1, "$etc$program.conf", undef), 'cache' => setv(T_FILE, 0, 0, 1, "$cachedir$program.cache", undef), 'pid' => setv(T_FILE, 0, 0, 1, "", undef), @@ -535,6 +536,7 @@ "usage: ${program} [options]", "options are:", [ "daemon", "=s", "-daemon delay : run as a daemon, specify delay as an interval." ], ++ [ "foreground", "!", "-foreground : do not fork" ], [ "proxy", "=s", "-proxy host : use 'host' as the HTTP proxy" ], [ "server", "=s", "-server host : update DNS information on 'host'" ], [ "protocol", "=s", "-protocol type : update protocol used" ], @@ -623,7 +625,10 @@ $SIG{'HUP'} = sub { $caught_hup = 1; }; $SIG{'TERM'} = sub { $caught_term = 1; }; $SIG{'KILL'} = sub { $caught_kill = 1; }; -if (opt('daemon') && !opt('force')) { +# don't fork() if foreground or force is on +if (opt('foreground') || opt('force')) { + ; +} elsif (opt('daemon')) { $SIG{'CHLD'} = 'IGNORE'; my $pid = fork; if ($pid < 0) { @@ -633,12 +638,15 @@ exit 0; } $SIG{'CHLD'} = 'DEFAULT'; - $opt{'syslog'} = 1; open(STDOUT, ">/dev/null"); open(STDERR, ">/dev/null"); open(STDIN, "</dev/null"); +} +# write out the pid file if we're daemon'ized +if(opt('daemon')) { write_pid(); + $opt{'syslog'} = 1; } umask 077; ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-17 22:30 Message: Thanks a lot drjohnny. I'm using your patch on Mac OS X 10.5.8 with launchd. I have attached the same patch applied against 3.8.0. All credit goes to drjohnny, mistakes are mine. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-18 09:28 Message: Logged In: YES user_id=722282 Originator: NO You're correct, I've made a mistake. Your patch could also be useful for debugging so I think I'll take closer look and maybe it will get included in the next release of ddclient. ---------------------------------------------------------------------- Comment By: John Palkovic (drjohnny) Date: 2008-02-14 01:02 Message: Logged In: YES user_id=985118 Originator: YES You are mistaken. fork() cannot be called, nor can exit() be reached to run properly under the control of runit or svscan. I want behavior like (apache2) httpd -DFOREGROUND or cron -f. ddclient -daemon=0 is not a daemon, it exits quickly on my debian etch box: # date Wed Feb 13 17:45:42 CST 2008 # time ddclient -daemon=0 -file /etc/ddclient.conf real 0m0.392s user 0m0.280s sys 0m0.036s This behavior is obvious if one glances at the while() statement on line 655 of 3.7.3. I want the program to loop in the do/while beginning on line 598 of version 3.7.3 without ever having called fork(). It should not exit() unless forced to by a signal or a restart. It must not call fork(). Do you understand? I don't think this functionality is available in the stock 3.7.3. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-14 00:00 Message: Logged In: YES user_id=722282 Originator: NO As far as I can see, you don't need a patch, you just need the daemon=0 option. I'm also wondering why you had some startup problems with the debian package. I didn't got any report about that from other people. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-17 20:30:59
|
Patches item #1893144, was opened at 2008-02-13 23:18 Message generated for change (Comment added) made by shmlchr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&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: Open Resolution: None Priority: 5 Private: No Submitted By: John Palkovic (drjohnny) Assigned to: wimpunk (wimpunk) Summary: Foreground patch Initial Comment: I am running ddclient as a dyndns.org client on a debian etch system. I had some problems with the startup script in the debian package. It was also out of date with no ssl support. I decided to patch ddclient to run under the control of runit (http://smarden.org/runit), a unix service supervisor akin to svscan (http://cr.yp.to/daemontools/svscan.html). I created the patch and have been running with it for a week with no issues to report. The patch adds a -foreground argument. When called with this argument, ddclient runs as a daemon but does not fork(). This is appropriate for use with runit or svscan (or launchd on a darwin system). There are changes to the daemon logic, so I would appreciate any comments. I will attach the patch with the upload button. -John Palkovic 13 Feb 2008 ---------------------------------------------------------------------- Comment By: Sam Homer (shmlchr) Date: 2009-08-17 22:30 Message: Thanks a lot drjohnny. I'm using your patch on Mac OS X 10.5.8 with launchd. I have attached the same patch applied against 3.8.0. All credit goes to drjohnny, mistakes are mine. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-18 09:28 Message: Logged In: YES user_id=722282 Originator: NO You're correct, I've made a mistake. Your patch could also be useful for debugging so I think I'll take closer look and maybe it will get included in the next release of ddclient. ---------------------------------------------------------------------- Comment By: John Palkovic (drjohnny) Date: 2008-02-14 01:02 Message: Logged In: YES user_id=985118 Originator: YES You are mistaken. fork() cannot be called, nor can exit() be reached to run properly under the control of runit or svscan. I want behavior like (apache2) httpd -DFOREGROUND or cron -f. ddclient -daemon=0 is not a daemon, it exits quickly on my debian etch box: # date Wed Feb 13 17:45:42 CST 2008 # time ddclient -daemon=0 -file /etc/ddclient.conf real 0m0.392s user 0m0.280s sys 0m0.036s This behavior is obvious if one glances at the while() statement on line 655 of 3.7.3. I want the program to loop in the do/while beginning on line 598 of version 3.7.3 without ever having called fork(). It should not exit() unless forced to by a signal or a restart. It must not call fork(). Do you understand? I don't think this functionality is available in the stock 3.7.3. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2008-02-14 00:00 Message: Logged In: YES user_id=722282 Originator: NO As far as I can see, you don't need a patch, you just need the daemon=0 option. I'm also wondering why you had some startup problems with the debian package. I didn't got any report about that from other people. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676130&aid=1893144&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-17 08:33:24
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7565895 By: cvinh Humm, you're right... thank you ! By the way, ddclient should not freeze like that, timeout should do its job, don't you think so ? I guess that if I want to have more reactivity for my IP change, I should check my IP on my router status webpage... I have a linksys WAG200G, I added the corresponding status page in ddclient : 'linksys-wag200g' => { 'name' => 'Linksys WAG200G FW', 'url' => '/setup.cgi?next_file=Status.htm', 'skip' => 'IP Address:', }, Regards ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-17 07:00:46
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7565749 By: wimpunk You get blocked because of your 60 seconds: see http://www.dyndns.com/developers/checkip.html for more information. As they say on the bottom of the place: Checks must be spaced 10 minutes apart to help reduce server load. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-16 21:46:41
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7565308 By: cvinh Thanks for replying so quick. My daemon runs every 60s but I only use dyndns.org to check my IP so dyndns does not block anything. I update my dns on ovh.com but it's not the problem as ddclient does not update if the cache matches the IP address. This is fine. The problem is that sometimes, the web page checkip.dyndns.org does not reply well (I am pretty sure it's because of our ISP here in French Polynesia that does have a transparent proxy, but we cannot do anything at this level...) Sometimes, the system timeout (180s for me) does well the job and ddclient does not freeze. Here are the logs to illustrate that behaviour : Aug 16 11:05:15 secure ddclient[30159]: CONNECT: checkip.dyndns.org Aug 16 11:05:15 secure ddclient[30159]: CONNECTED: using HTTP Aug 16 11:05:15 secure ddclient[30159]: SENDING: GET / HTTP/1.0 Aug 16 11:05:15 secure ddclient[30159]: SENDING: Host: checkip.dyndns.org Aug 16 11:05:15 secure ddclient[30159]: SENDING: User-Agent: ddclient/3.8.0 Aug 16 11:05:15 secure ddclient[30159]: SENDING: Connection: close Aug 16 11:05:15 secure ddclient[30159]: SENDING: Aug 16 11:08:16 secure ddclient[30159]: RECEIVE: HTTP/1.1 200 OK#015 Aug 16 11:08:16 secure ddclient[30159]: WARNING: TIMEOUT: checkip.dyndns.org after 120 seconds Aug 16 11:08:16 secure ddclient[30159]: WARNING: unable to determine IP address But sometimes, the timeout does not work... Here are my last logs before the daemon freezed again. Now it's 11:27, it's been 10 minutes it's stucked. Aug 16 11:16:27 secure ddclient[30159]: CONNECT: checkip.dyndns.org Aug 16 11:16:27 secure ddclient[30159]: CONNECTED: using HTTP Aug 16 11:16:27 secure ddclient[30159]: SENDING: GET / HTTP/1.0 Aug 16 11:16:27 secure ddclient[30159]: SENDING: Host: checkip.dyndns.org Aug 16 11:16:27 secure ddclient[30159]: SENDING: User-Agent: ddclient/3.8.0 Aug 16 11:16:27 secure ddclient[30159]: SENDING: Connection: close Aug 16 11:16:27 secure ddclient[30159]: SENDING: Aug 16 11:16:28 secure ddclient[30159]: RECEIVE: HTTP/1.1 200 OK#015 Aug 16 11:16:28 secure ddclient[30159]: RECEIVE: Content-Type: text/html#015 Aug 16 11:16:28 secure ddclient[30159]: RECEIVE: Server: DynDNS-CheckIP/1.0#015 Aug 16 11:16:28 secure ddclient[30159]: RECEIVE: Cache-Control: no-cache#015 Aug 16 11:16:28 secure ddclient[30159]: RECEIVE: Pragma: no-cache#015 Aug 16 11:16:29 secure ddclient[30159]: RECEIVE: Content-length: 105#015 Aug 16 11:16:29 secure ddclient[30159]: RECEIVE: Connection: close#015 Aug 16 11:16:29 secure ddclient[30159]: RECEIVE: Date: Sun, 16 Aug 2009 21:16:28 GMT#015 Aug 16 11:16:29 secure ddclient[30159]: RECEIVE: #015 Aug 16 11:16:29 secure ddclient[30159]: RECEIVE: <html><head><title>Current IP Check</title></head><body>Current IP Address: 202.90.76.180</body></html>#015 Aug 16 11:16:29 secure ddclient[30159]: SUCCESS: pf-easypme.invitu.com: skipped: IP address was already set to 202.90.76.180. Aug 16 11:17:29 secure ddclient[30159]: CONNECT: checkip.dyndns.org Aug 16 11:17:29 secure ddclient[30159]: CONNECTED: using HTTP Aug 16 11:17:29 secure ddclient[30159]: SENDING: GET / HTTP/1.0 Aug 16 11:17:29 secure ddclient[30159]: SENDING: Host: checkip.dyndns.org Aug 16 11:17:29 secure ddclient[30159]: SENDING: User-Agent: ddclient/3.8.0 Aug 16 11:17:29 secure ddclient[30159]: SENDING: Connection: close Aug 16 11:17:29 secure ddclient[30159]: SENDING: ... and that's it Here's my conf file : daemon=60 # check every 60 seconds syslog=yes # log update msgs to syslog mail=root # mail all msgs to root mail-failure=root # mail failed update msgs to root pid=/var/run/ddclient.pid # record PID in file. ssl=yes # use ssl-support. Works with verbose=yes debug=yes timeout=20 use=web protocol=dyndns2 server=www.ovh.com login=invitu.com-easypme password=******* pf-easypme.invitu.com the full result of `ddclient -daemon=0 -debug -verbose -noquiet` does not show more logs. Do you think you would still need it ? (it's hard to catch it as the problem occurs randomly and I must wait 3 minutes to check if the timeout works or not) PS: I tried with the last svn rev111, same thing I tried the modification found in the bug 2113169 but I have a segfault... Actually, the only solution I found is to restart ddclient every hour which is not elegant... Regards ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-16 19:06:57
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7565115 By: wimpunk Could you please post the full result of `ddclient -daemon=0 -debug -verbose -noquiet` and try to understand the logging. If you don't understand or find an error, post your config and the result on http://ddclient.pastebin.ca and post a link here. If you have a daemon setting less than 600, your just blocked by dyndns. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-16 18:44:23
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7565097 By: cvinh Hello This problem seems to be present in 3.8.0 as I can reproduce it several times. I use web checkip on dyndns.org The daemon is stuck just after it sends the http request : # ps aux |grep ddclient root 26917 0.0 2.1 10620 5584 pts/0 S 08:13 0:00 ddclient - reading from checkip.dyn Here are my /var/log/messages : Aug 16 08:25:57 secure ddclient[26917]: CONNECT: checkip.dyndns.org Aug 16 08:25:57 secure ddclient[26917]: CONNECTED: using HTTP Aug 16 08:25:57 secure ddclient[26917]: SENDING: GET / HTTP/1.0 Aug 16 08:25:57 secure ddclient[26917]: SENDING: Host: checkip.dyndns.org Aug 16 08:25:57 secure ddclient[26917]: SENDING: User-Agent: ddclient/3.8.0 Aug 16 08:25:57 secure ddclient[26917]: SENDING: Connection: close Aug 16 08:25:57 secure ddclient[26917]: SENDING: ... and nothing more... It seems to be related to bug #2113169 https://sourceforge.net/tracker/?func=detail&aid=2113169&group_id=116817&atid=67 6128 ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-16 17:57:30
|
Bugs item #2113169, was opened at 2008-09-16 00:24 Message generated for change (Comment added) made by cvinh You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2113169&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: Other Group: None Status: Open Resolution: None Priority: 4 Private: No Submitted By: kostos (kostos) Assigned to: wimpunk (wimpunk) Summary: Timeout option doesn't prevent hangs Initial Comment: Hi, i have Aolynk DR814 ADSL modem which is hanging from time to time and wifi-router (Dlink) connected between ADSL modem and server running ddclient. In this configiration, when ADSL modem hangs, ddclient also hanging with message like " ddclient - read from 192.168.1.1 .." and still hanged infinitely, even after modem restarted, regardless timeout option is set. As W/A i have changed the source code line below: local $SIG{'ALRM'} = sub { $timeout = 1; }; to close socket descriptor when timeout happens: local $SIG{'ALRM'} = sub { $timeout = 1; close($sd);}; Not sure is it good enough solution, but after week of testing (2 or 3 hangs happened) - it seem working, ddclient didn't hang since. Could you please check if it possible to include similar change into release? P.S. Could you also please consider small extension of functionality: in my feeling, it would be not too bad idea to log error message when timeout happens, or even better - to call external script given by option parameter to try to fix the issue. ---------------------------------------------------------------------- Comment By: Cyril VINH-TUNG (cvinh) Date: 2009-08-16 17:57 Message: Hello I have exactly the same problem with web checkip. ddclient hangs at : CONNECT: checkip.dyndns.org CONNECTED: using HTTP SENDING: GET / HTTP/1.0 SENDING: Host: checkip.dyndns.org SENDING: User-Agent: ddclient/3.7.3 SENDING: Connection: close SENDING: I tried to modify the script with local $SIG{'ALRM'} = sub { $timeout = 1; close($sd);}; but I have a segfault after timeout (20s) and ddclient daemon crashes : Aug 16 07:41:53 videosurvey ddclient[8215]: CONNECT: checkip.dyndns.org Aug 16 07:41:54 videosurvey ddclient[8215]: CONNECTED: using HTTP Aug 16 07:41:54 videosurvey ddclient[8215]: SENDING: GET / HTTP/1.0 Aug 16 07:41:54 videosurvey ddclient[8215]: SENDING: Host: checkip.dyndns.org Aug 16 07:41:54 videosurvey ddclient[8215]: SENDING: User-Agent: ddclient/3.7.3 Aug 16 07:41:54 videosurvey ddclient[8215]: SENDING: Connection: close Aug 16 07:41:54 videosurvey ddclient[8215]: SENDING: Aug 16 07:42:14 videosurvey kernel: ddclient[8215]: segfault at 8 ip 002abf9c sp bfdb7a70 error 6 in libperl.so[101000+257000] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676128&aid=2113169&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-11 09:37:40
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7555185 By: wimpunk I didn't had the time to update the documents but this could be a good start: https://sourceforge.net/mailarchive/message.php?msg_id=20080924120754.GA15984%40 astaro.com ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-11 02:55:08
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7554717 By: plwrenn I was just looking for the same information. I also have two external interfaces that I would like to setup. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-05 21:14:18
|
Feature Requests item #2832129, was opened at 2009-08-04 17:20 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&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: Access to other dyndns service providers Group: None >Status: Closed Priority: 5 Private: No Submitted By: Alexander Dupuy (dupuy) Assigned to: wimpunk (wimpunk) Summary: support for freedns.afraid.org Initial Comment: John Haney posted a patch for freedns.afraid.org support back in December 2008: https://sourceforge.net/forum/forum.php?thread_id=2681547&forum_id=399427 I have reformatted his patch slightly to match the whitespace and bracing style of ddclient, and attached it to this feature request. .conf file example is: protocol=freedns, \ login=my-freedns.afraid.org-login, \ password=my-freedns.afraid.org-password \ myhost.afraid.com ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-08-05 21:14 Message: Patch applied in r111 ---------------------------------------------------------------------- Comment By: Alexander Dupuy (dupuy) Date: 2009-08-05 17:34 Message: I have uploaded a better patch (which actually works on 3.8.0 - there was a minor change in getting $ip since 3.7.3 and the previous patch did not work with 3.8.0). It now will only attempt to load Digest::SHA1 iff there is an entry with protocol=freedns (failure to load the module is, however, fatal). I also improved some of the error checking and logging a little bit, to avoid undefined variable errors if the server is specified incorrectly, or -verbose is specified. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2009-08-05 15:00 Message: I saw you posted a message on the forum: https://sourceforge.net/forum/message.php?msg_id=7544221 ---------------------------------------------------------------------- Comment By: Alexander Dupuy (dupuy) Date: 2009-08-04 17:48 Message: One potential disadvantage of the patch as I posted it (from John Haney) is the presence of the "use Digest::SHA1" which creates a dependency on that perl module even in configurations where no freedns servers are configured. This could be worked around by removing that "use" line, and adding something like this to the top of nic_freedns_update: if (!eval "require Digest::SHA1; import Digest::SHA1 (qw/sha1_hex/);") { failed("could not load Digest::SHA1: $@"); return; } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-05 17:36:14
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7546449 By: dupuy I uploaded an improved version of the patch which addresses this issue (and some other problems with the original). ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-05 17:34:57
|
Feature Requests item #2832129, was opened at 2009-08-04 13:20 Message generated for change (Comment added) made by dupuy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&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: Access to other dyndns service providers Group: None Status: Open Priority: 5 Private: No Submitted By: Alexander Dupuy (dupuy) Assigned to: wimpunk (wimpunk) Summary: support for freedns.afraid.org Initial Comment: John Haney posted a patch for freedns.afraid.org support back in December 2008: https://sourceforge.net/forum/forum.php?thread_id=2681547&forum_id=399427 I have reformatted his patch slightly to match the whitespace and bracing style of ddclient, and attached it to this feature request. .conf file example is: protocol=freedns, \ login=my-freedns.afraid.org-login, \ password=my-freedns.afraid.org-password \ myhost.afraid.com ---------------------------------------------------------------------- Comment By: Alexander Dupuy (dupuy) Date: 2009-08-05 13:34 Message: I have uploaded a better patch (which actually works on 3.8.0 - there was a minor change in getting $ip since 3.7.3 and the previous patch did not work with 3.8.0). It now will only attempt to load Digest::SHA1 iff there is an entry with protocol=freedns (failure to load the module is, however, fatal). I also improved some of the error checking and logging a little bit, to avoid undefined variable errors if the server is specified incorrectly, or -verbose is specified. ---------------------------------------------------------------------- Comment By: wimpunk (wimpunk) Date: 2009-08-05 11:00 Message: I saw you posted a message on the forum: https://sourceforge.net/forum/message.php?msg_id=7544221 ---------------------------------------------------------------------- Comment By: Alexander Dupuy (dupuy) Date: 2009-08-04 13:48 Message: One potential disadvantage of the patch as I posted it (from John Haney) is the presence of the "use Digest::SHA1" which creates a dependency on that perl module even in configurations where no freedns servers are configured. This could be worked around by removing that "use" line, and adding something like this to the top of nic_freedns_update: if (!eval "require Digest::SHA1; import Digest::SHA1 (qw/sha1_hex/);") { failed("could not load Digest::SHA1: $@"); return; } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-05 15:13:38
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7546197 By: wimpunk Your patch looks great but as you mentioned yourself: your use-statement isn't on the good place for it. It would be nice if you could modify the code so ddclient checks at the start if it needs Digest::SHA1, try to load it if needed and gives an error if it doesn't work. If you could do so, I will certainly apply the patch. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-05 15:00:21
|
Feature Requests item #2832129, was opened at 2009-08-04 17:20 Message generated for change (Comment added) made by wimpunk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&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: Access to other dyndns service providers Group: None Status: Open Priority: 5 Private: No Submitted By: Alexander Dupuy (dupuy) Assigned to: wimpunk (wimpunk) Summary: support for freedns.afraid.org Initial Comment: John Haney posted a patch for freedns.afraid.org support back in December 2008: https://sourceforge.net/forum/forum.php?thread_id=2681547&forum_id=399427 I have reformatted his patch slightly to match the whitespace and bracing style of ddclient, and attached it to this feature request. .conf file example is: protocol=freedns, \ login=my-freedns.afraid.org-login, \ password=my-freedns.afraid.org-password \ myhost.afraid.com ---------------------------------------------------------------------- >Comment By: wimpunk (wimpunk) Date: 2009-08-05 15:00 Message: I saw you posted a message on the forum: https://sourceforge.net/forum/message.php?msg_id=7544221 ---------------------------------------------------------------------- Comment By: Alexander Dupuy (dupuy) Date: 2009-08-04 17:48 Message: One potential disadvantage of the patch as I posted it (from John Haney) is the presence of the "use Digest::SHA1" which creates a dependency on that perl module even in configurations where no freedns servers are configured. This could be worked around by removing that "use" line, and adding something like this to the top of nic_freedns_update: if (!eval "require Digest::SHA1; import Digest::SHA1 (qw/sha1_hex/);") { failed("could not load Digest::SHA1: $@"); return; } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-04 17:48:54
|
Feature Requests item #2832129, was opened at 2009-08-04 13:20 Message generated for change (Comment added) made by dupuy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&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: Access to other dyndns service providers Group: None Status: Open Priority: 5 Private: No Submitted By: Alexander Dupuy (dupuy) Assigned to: wimpunk (wimpunk) Summary: support for freedns.afraid.org Initial Comment: John Haney posted a patch for freedns.afraid.org support back in December 2008: https://sourceforge.net/forum/forum.php?thread_id=2681547&forum_id=399427 I have reformatted his patch slightly to match the whitespace and bracing style of ddclient, and attached it to this feature request. .conf file example is: protocol=freedns, \ login=my-freedns.afraid.org-login, \ password=my-freedns.afraid.org-password \ myhost.afraid.com ---------------------------------------------------------------------- >Comment By: Alexander Dupuy (dupuy) Date: 2009-08-04 13:48 Message: One potential disadvantage of the patch as I posted it (from John Haney) is the presence of the "use Digest::SHA1" which creates a dependency on that perl module even in configurations where no freedns servers are configured. This could be worked around by removing that "use" line, and adding something like this to the top of nic_freedns_update: if (!eval "require Digest::SHA1; import Digest::SHA1 (qw/sha1_hex/);") { failed("could not load Digest::SHA1: $@"); return; } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-08-04 17:24:28
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7544221 By: dupuy There wasn't exactly an outrush of answers to this question, but eventually I did find a way to make this work. It does require a patch to ddclient, which I got from this forum itself - John Hanely posted it in December 2008: https://sourceforge.net/forum/forum.php?thread_id=2681547&forum_id=399427 Cutting and pasting the patch from the forum wasn't particularly successful, as it lost all the whitespace formatting, but I recreated it (against the current 3.8.0) and submitted it as SourceForge feature request ID 2832129: https://sourceforge.net/tracker/?func=detail&aid=2832129&group_id=116817&atid=676131 - with luck this may get incorporated into the mainstream, if not at least the next person who needs this can apply the patch more easily by downloading the attachment from the feature request. @alex ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=399428 |
From: SourceForge.net <no...@so...> - 2009-08-04 17:20:28
|
Feature Requests item #2832129, was opened at 2009-08-04 13:20 Message generated for change (Tracker Item Submitted) made by dupuy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&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: Access to other dyndns service providers Group: None Status: Open Priority: 5 Private: No Submitted By: Alexander Dupuy (dupuy) Assigned to: wimpunk (wimpunk) Summary: support for freedns.afraid.org Initial Comment: John Haney posted a patch for freedns.afraid.org support back in December 2008: https://sourceforge.net/forum/forum.php?thread_id=2681547&forum_id=399427 I have reformatted his patch slightly to match the whitespace and bracing style of ddclient, and attached it to this feature request. .conf file example is: protocol=freedns, \ login=my-freedns.afraid.org-login, \ password=my-freedns.afraid.org-password \ myhost.afraid.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=676131&aid=2832129&group_id=116817 |
From: SourceForge.net <no...@so...> - 2009-07-14 07:55:29
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7501346 By: wimpunk this has been asked before: https://sourceforge.net/forum/message.php?msg_id=2794344 ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=467339 |
From: SourceForge.net <no...@so...> - 2009-07-14 00:46:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7500453 By: renichbon Please, add support for these guys. They're incredible. Here's the info you need (near the EOF) http://www.dnsexit.com/Direct.sv?cmd=ipClients ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=467339 |