foo log

[Kevin Darcy]

Well, what command line does /etc/rc2.d/init.d/named on your box use to start
named? Maybe it specifies some "example" configuration that is creating the
"foo" log file. Instead of just guessing, why don't you look in that startup
script?

BTW, what OS and version is this? You neglected to mention.


- Kevin

mjs wrote:

> WOW!..this is odd,..i installed BIND 8.2.3 from scratch, running
> make
> make clean
> make depend
> mak all
>
> and before doing 'make install' I deleted the .settings file in the src dir
> and edited the /src/port/linux Makefile.set to alter the DESTINATION dir to
> /usr/local/bind823 and its child dir
> DESTSBIN=/usr/local/bind823/sbin
> DESTBIN/usr/local/bind823/bin
>
> etc,..etc.....
>
> afer this,...I placed the startup script call named in /etc/rc.d/init.d/
> then I ran chkconfig --add named
> chkconfig --level 345 named on
>
> all went fine at this point,...but here is where it gets wierd, after
> starting the named daemon by running
> /etc/rc.d/init.d/named start
> which went fine and started ok.....but what was strange was it created a log
> file in /root called 'foo'
>
> i used jove to open it,.and yep, it was a log file for the named daemon,..so
> I went ahead and deleted it, but every time i start up the named daemon
> using /etc/rc.d/init.d/named start it re-created it but when i just start
> named with the path like /usr/local/bind823/sbin/named -u named
> it doesn't create this 'foo' named log
>
> WHATS going on here??...any thoughts??,..I'm truly baffled
>
> thanks
>
> ____________________________________________
>
>  An optimist believes we live in the best of all  possible worlds.  A
> pessimist is sure of it!
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.237 / Virus Database: 115 - Release Date: 3/7/2001