Wrong init script for djbdns

Binary package hint: djbdns-installer

djbdns-installer-1.05-11 on Dapper builds a djbdns-1.05-11 package containing an /etc/init.d/djbdns script.

The script is a little confusing just for its presence: not placing any symlink in rcX.d dirs will not result in the service not starting, since it's controlled by svscan and not from init.d scripts, making this a little different from all other init.d services. Making 'K' symlinks to stop the service is not a clean solution, either: the service(s) will be started by svscan at every boot and will run for some time (even if not much) before rc will call init.d/djbdns stop.

The script wouldn't even work due to path problems:
1) it has '/var/lib/svscan/' hardcoded as the service directory, when the default choice in build-daemontools is to follow DJB-style paths, with /service as directory. Thus if the user follows all the scripts' suggestions will have services in a place and init.d/djbdns looking for them in another place. And no, it's not even symlinked.
2) it looks for dnscache*, tinydns*, axfrdns* service directories. A user could use different names for his services, or could use those names for non-djbdns services (I understand this isn't common at all, but it's still technically possible), or could use other services from the djdbns package (namely walldns, pickdns, rbldns) not accounted for in the init.d/djbdns script.

That script shouldn't be there (AFAIK it's not part of DJB's software upstream but it's a debian and/or ubuntu addition). If it's there it is using a service path different from the default one. And if the user chooses the non-default FHS-style path for the service directory, the script only tries to work on three out of six possible services. IMHO that script should be considered a bug.

Since djbdns daemons are normally managed by svscan, I suggest to completely remove the init.d/djbdns script from the package asap.