Hi! We are currently deploying a big scale Debian-based Communication Service for Schools.
All the machines scattered around should claim their dns-name via nsupdate, when they dial in. Now I get real weird behaviour with nsupdate from dnsutils package in stable. The documentation is really broken already (reported bug) and (what's much worse) the same binary (according to md5sum) of nsupdate behaves differently on two machines. nsupdate -k /etc/bind/:name.second-level.toplevel. works on one of them. This seems to be a new form used in the packages from testing and unstable. Some of the machines require nsupdate -k /etc/bind/filename-to-key Neither does work with the others option. Strange, no? When I do an strace I see that the nsupdate which runs with the strange syntax (with ":") does a chdir() to the directory and then contructs a correct filename whereas the second example directly uses open() on the supplied argument. Anyone also having this problem? Any pointers? Are there configuration files which might differ (it is the SAME binary, goddammit)? tia, Florian -- Florian Thiel - Medienzentrum Kassel Systembetreuung Internet- und Kommunikationstechnik Kasseler Schulen am Netz - http://www.medienzentrum-kassel.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
