Your message dated Wed, 5 Apr 2006 01:03:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Still working, no activity, closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: ddclient
Version: 3.6.2-3.1
Severity: important
Debconf generates an invalid config file /etc/ddclient.conf. The options
are basicly in the wrong order so that ddclient can't update your DNS
information. For example:
My config file after debconf looked like this:
pid=/var/run/ddclient.pid
protocol=dyndns2
use=if, if=ppp0
server=dyndns.noxa.de
login=mylogin
password=mypassword
myhost.h3c.de
With this settings it won't update my DNS information and the update
server complains about missing authentication.
Correct and working are/is the following settings/order:
pid=/var/run/ddclient.pid
login=mylogin
password=mypassword
use=if, if=ppp0
server=dyndns.noxa.de, \
protocol=dyndns2 \
myhost.h3c.de
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-386
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages ddclient depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii perl [perl5] 5.8.4-8 Larry Wall's Practical Extraction
-- debconf information:
* ddclient/run_daemon: false
* ddclient/interface: ppp0
* ddclient/protocol: dyndns2
* ddclient/run_ipup: true
* ddclient/username: mylogin
ddclient/newconfigfmt:
* ddclient/names: myhost.h3c.de
ddclient/modifiedconfig:
* ddclient/server: dyndns.noxa.de
ddclient/daemon_interval: 300
* ddclient/service: other
--- End Message ---
--- Begin Message ---
Hi Jonathan,
This bug report did not see any activity for ages. I am still not able
to reproduce it and the debconf generated configuration is still working
fine for me on multiple systems. As I did not get even a single "me too"
for your report, I guess that this is not really a bug. No idea why it
did not work - let's move on until it happens again :-)
As always, feel free to object and give me some more evidence while
you are at it.
Greetings
Torsten
signature.asc
Description: Digital signature
--- End Message ---
