On 2005-05-01 14:57, Fafa Diliha Romanova <[EMAIL PROTECTED]> wrote:
>"Ed Stover" <[EMAIL PROTECTED]> wrote:
>>>> First off, what have you done with that machine before it stopped
>>>> working? when you try to start named does it produce any error
>>>> messages?
>>
>> You are not being helpful. lol, try this
>> /usr/local/etc/rc.d/bind start
>> ps -ax |grep named
>> Now is there a named running?
>
> Hehe :) Yeah named is running.
>
> /etc/rc.d/named start && ps -ax | grep named:
>
> 247 ?? Ss 0:00.79 /usr/sbin/syslogd -l /var/run/log -l
> /var/named/var/run/log -s
> 261 ?? Ss 0:37.36 /usr/sbin/named -u bind -t /var/named
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.
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.
- Giorgos
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
