error message on NAMEDB_MAGIC inconsistency
Miek Gieben
miekg at atoom.net
Fri Jan 7 08:57:03 UTC 2005
[On 07 Jan, @ 07:36, Koh-ichi wrote in "error message on NAMEDB_MAGIC ..."]
> Hello,
>
> I got an error message like the following:
>
> Jan 7 12:13:52 myhost nsd[92737]: corrupted database: /var/db/nsd.db
> Jan 7 12:13:52 myhost nsd[92737]: unable to load /var/db/nsd.db: No such file or directory
>
<SNIP>
> with the error, so to call strerror() sounds inapropriate, I
> think.
>
> How?
yes, you're right, but I don't see a quick fix.
namedb_open() returns NULL on error, so there is currently no
difference between a database error or a 'file not found' error.
Maybe dropping the whole log_msg() from server.c would be an idea,
and leave the error reporting in namedb_open().
grtz Miek
More information about the nsd-users
mailing list