On 7 Jan 1999, Graeme Bell writes:
> Yeah, I have a terminal running tail -f on messages and maillog and
> secure, but with the "option querylog" in named.boot, and no "-q"
> option the messages log just sits there lookin' stoopid. :-) So I
> must be doing something wrong. Do I need to set a logging level
> option somewhere? (There's nothing about that that I could find).
Did you not check the named man page?
That manpage says (on my R 5.2 system at least, with bind-8.1.2-5
installed):
-q Trace all incoming queries if NAMED has been compiled with
QRYLOG defined.
NOTE: This option is deprecated in favor of the ``queries''
logging category of the configuration file's ``logging''
statement; for more information, please refer to the configu-
ration file guide included with this distribution of BIND.
Most likely, then, the named binary you are running was not compiled
with the QRYLOG option. -q is a deprecated option nowadays! Either
do what the man page says about the new style logging statement in
your named.conf file, or else grab the source RPM and roll your own
named after ensuring QRYLOG gets defined in the Makefile.
For the former, try something like
logging {
category queries { default_syslog; default_debug; };
}
in your named.conf. Sadly RH dails to include the BIND docs if you
only install the binary RPM, I don't know why. So you have to grab
the SRPM and install it and rpm -bp it, and then go read the
docs... :-(
If you still get nowhere, check that syslogd is behaving itself.
Use logger to check what levels of information you are actually
logging to /var/log/messages.
echo will this be logged | logger -p daemon.info
will log the message 'will this be logged' to the daemon facility at debug
priority. Does that entry show up in /var/log/messages OK?
If it does, the command
killall -HUP named
should (as in, really really should) generate some entries in
/var/log/messages as named rereads its config files and reinitializes
itself. The command
/etc/rc.d/init/named restart
is another way to do this.
If you still get no output at all to /var/log/messages, check your
/etc/syslog.conf file to see just what you are telling syslog to put
in that file, and edit the file and send a HUP to syslogd if
necessary.
If that doesn't help, do the techie thing: read the BIND source code!
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
