Displaying 6 results from an estimated 6 matches for "datalimit".
2015 Jan 13
3
DJBDNS: very weird dnscache issue
...pled did the load
exceed 200 requests per second. In tests conducted earlier the DNS server
successfully demonstrated speeds in tens of thousands of requests per
second.
We then proceeded to edit the following parameters in the dnscache.conf as
they seemed to be the only ones that seemed relevant: DATALIMIT and
CACHESIZE. They are described as limints (in bytes) on the total data
memory allocation and cache, default values are 80000000 and 50000000
respectively.
Playing with these demonstrated some highly counterintuitive results:
1) Setting the values lower (say, an order of magnitude lower) made t...
2015 Jan 14
2
DJBDNS: very weird dnscache issue
...ests conducted earlier the DNS server
> > successfully demonstrated speeds in tens of thousands of requests per
> > second.
> >
> > We then proceeded to edit the following parameters in the dnscache.conf
> as
> > they seemed to be the only ones that seemed relevant: DATALIMIT and
> > CACHESIZE. They are described as limints (in bytes) on the total data
> > memory allocation and cache, default values are 80000000 and 50000000
> > respectively.
> >
> > Playing with these demonstrated some highly counterintuitive results:
> >
> > 1...
2015 Jan 13
0
DJBDNS: very weird dnscache issue
...200 requests per second. In tests conducted earlier the DNS server
> successfully demonstrated speeds in tens of thousands of requests per
> second.
>
> We then proceeded to edit the following parameters in the dnscache.conf as
> they seemed to be the only ones that seemed relevant: DATALIMIT and
> CACHESIZE. They are described as limints (in bytes) on the total data
> memory allocation and cache, default values are 80000000 and 50000000
> respectively.
>
> Playing with these demonstrated some highly counterintuitive results:
>
> 1) Setting the values lower (say,...
2015 Jan 15
0
DJBDNS: very weird dnscache issue
...he DNS server
>> > successfully demonstrated speeds in tens of thousands of requests per
>> > second.
>> >
>> > We then proceeded to edit the following parameters in the dnscache.conf
>> as
>> > they seemed to be the only ones that seemed relevant: DATALIMIT and
>> > CACHESIZE. They are described as limints (in bytes) on the total data
>> > memory allocation and cache, default values are 80000000 and 50000000
>> > respectively.
>> >
>> > Playing with these demonstrated some highly counterintuitive results:
&...
2014 Oct 27
1
tinydns exceeds "holdoff time" on startup under CentOS 7
...start tinydns
they start just fine.
>From the log I got the following for tinydns:
Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting: Oct-24
2014 15:01:43 EDT
Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DEBUG_LEVEL set to `1'
Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DATALIMIT set to `300000' bytes
Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: could not bind UDP socket
Oct 24 15:01:43 ns99 systemd[1]: tinydns.service holdoff time over,
scheduling restart.
Any idea why that would happen? Any idea how to increase the holdoff time
in the configuration?
The config for t...
2003 Dec 01
0
No subject
...I have a PE 2400 with 48Gb of data.
I personally find Arkeia a good backup solution. It has a complete graphical
java based user internface that runs under Linux and Windows.They even do
have a free version for commercial use with limitted posibilitys (One server,
two clients only I think, no datalimit and no time limit).
I run it on a Debian system and works just fine, I do know they have a Suse
and a RH version to.
Go to www.arkeia.com and see for your self.
I also know that arcserve has a Linux version but never worked with that one
on linux.
Greets,
Ries
Return-Path: <alastair_brown@y...