> Please do __NOT__ post your reply on top of a long quoted part of the > original. Both top-posting and failing to trim quoted material to the > absolutely minimum necessary size are considered "bad netiquette" on > this list.
Sorry! > Having said that, you can check your /var/log/messages for interesting > bits sent there by the named process as it starts: > > # tail -f /var/log/messages | grep named > > Then, restart your named and watch for interesting output. > > For extra bonus points, you can add a special "named" entry in your > /etc/syslog.conf file: > > !named > *.* /var/log/named.log > > which will direct only the messages from named to a special log file. > Remember to restart syslogd after you add this to syslog.conf and then > use tail -f on the named.log file to watch for named output. > > Then, after having all the necessary information from a named reload, > you may have more hints and/or clues about what's wrong. There has never been anything interesting in /var/log, I am afraid. My world and kernel are making to solve this problem, though :) http://lists.freebsd.org/pipermail/freebsd-questions/2005-May/085943.html -- Fafa Hafiz Krantz Senior Designer @ http://www.home.no/barbershop Furious @ http://www.home.no/barbershop/smart/sharon.pdf -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
