You are can run named with option "-S 8096" or more.
Also increase file limits in /etc/security/limits.conf
* softnofile 8192
On 12/02/2014 07:23 AM, PORTER, BLAIR wrote:
>
> Hello, I recently compiled Bind 9.9.6, on RedHatas follows:
>
>
>
> BIND 9.9.6-S2 (Subscription Edition) bui
Hello, I recently compiled Bind 9.9.6, on RedHatas follows:
BIND 9.9.6-S2 (Subscription Edition) built by make with
'--enable-threads' '--enable-fixed-rrset' '--disable-openssl-version-check'
'--with-openssl=no'
compiled by GCC 4.1.2 20080704 (Red Hat 4.1.2-52)
All seemed ok, except for 1 part
Ok , Thank you
2014-12-01 10:49 GMT+00:00 Tony Finch :
> Kaouthar Chetioui wrote:
> >
> > I don't find any name of source file (like message.c or name.c) or name
> of
> > function in this log file, so I can't understand excatly the process of
> > resolution for dig command.
>
> The log module gi
Kaouthar Chetioui wrote:
>
> I don't find any name of source file (like message.c or name.c) or name of
> function in this log file, so I can't understand excatly the process of
> resolution for dig command.
The log module gives you a rough idea of which part of the system emitted
the log message
thank very much for your answer,
I have done it, and when I look at log file, I found a lot of information
like this:
29-Nov-2014 18:09:58.121 general: debug 60: sockmgr 0xb77d7008: watcher got
message -3 for socket 514
29-Nov-2014 18:09:58.121 general: debug 60: sockmgr 0xb77d7008: watcher got
m
On 11/28/2014 02:10 PM, Daniel Ryšlink wrote:
> Happened in dig from bind-tools 9.9 and 9.10, both on Linux and FreeBSD.
>
> After issuing the following command, dig ends with a core dump:
>
> dig +trace +topdown +sigchase +trusted-key=./key.txt rhybar.cz mx
>
> Launch a query to find a RRset of ty
6 matches
Mail list logo
