None, whatsoever. Have you scanned the source code for it?
On Tue, 13 Mar 2001, mjs wrote:
> I understand this ..and I dont' have any reference to logs in my named.conf,
> this is why Im baffled about this log named foo being created in /root every
> time I start my named daemon using the startup script /etc/rc.d/init.d/named
> start
>
> and also why it opens port 52 with the name xns-time
>
> I've checked for any line with 'foo' to find out why its being created with
> NO luck...
>
> If you can think of any reason for this,..please let me know..
>
>
> Thanks ..
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Burger
> Sent: Tuesday, March 13, 2001 9:27 AM
> To: REDHAT . .
> Subject: Re: strange log
>
>
> In your named.conf file, you can specify what you want to log and where
> you want to log it. Observe:
>
> logging {
> channel my_syslog { file "/var/log/named/named.log" versions 5;
> severity info;
> print-category yes;
> print-time yes;
> };
> channel my_lame { file "/var/log/named/lame.log" versions 5;
> severity info;
> print-category yes;
> print-time yes;
> // size 50M;
> };
> channel my_xfer { file "/var/log/named/xfer.log" versions 5;
> severity info;
> print-category yes;
> print-time yes;
> // size 50M;
> };
> channel my_update { file "/var/log/named/named.update" versions 5;
> severity info;
> print-category yes;
> print-time yes;
> // size 50M;
> };
> channel my_db { file "/var/log/named/db.log" versions 5;
> severity info;
> print-category yes;
> print-time yes;
> // size 50M;
> };
> channel my_query { file "/var/log/named/query.log" versions 2;
> severity info;
> print-category yes;
> print-time yes;
> // size 50M;
> };
> channel my_security { file "/var/log/named/security.log" versions
> 99;
> severity info;
> print-category yes;
> print-time yes;
> // size 50M;
> };
> channel my_debug { file "/var/log/named/named.debug" versions 20;
> severity dynamic;
> print-category yes;
> print-time yes;
> // size 50M;
> };
>
>
> category security { my_security; };
> category default { my_syslog; };
> category queries { my_query; };
> category lame-servers { my_lame; };
> category update { my_update; };
> category db { my_db; };
> category xfer-in { my_xfer; };
> category xfer-out { my_xfer; };
> category packet { null; };
> category eventlib { my_syslog; };
>
>
> };
>
>
> On Tue, 13 Mar 2001, mjs wrote:
>
> > I'm running RH 6.2 this is odd,..i installed BIND 8.2.3 from scratch,
> > running
> >
> > make clean
> > make depend
> > mak all
> > make install
> >
> > 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
> >
> > AND on top of that, I ran NMAP on my ip and it showed domain on port 53
> but
> > also something called xns-time on port 52 ..so i checked to see what
> process
> > was using this port and sure enough, it was the named daemom.
> >
> > 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
> >
> >
> >
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> >
>
>
>
>
> ---
> Incoming 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
>
> ---
> 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
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
