Displaying 20 results from an estimated 100 matches similar to: "Processing "BIND8-like" statistics"
2008 Jan 15
1
problem using nsd
Hello I have this problem since a week or so:
The nsd daemon crashes unexpectedly and the nsd log files shows this:
[1200299533] nsd[3736]: info: XSTATS 1200299533 1200298484 RR=0 RNXD=0
RFwdR=0 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=0
SAns=40 SFwdQ=0 SDupQ=0 SErr=0 RQ=37 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=0
SFail=30 SFErr=0 SNaAns=0 SNXD=0 RUQ=0 RURQ=0 RUXFR=0 RUUpd=1
2001 Sep 01
0
Uneditted logfile for my ppp+tinc messup
Blame guus.
--
Rob 'robster' Bradford
Chief Editor/Lead developer
DebianPlanet.org
-------------- next part --------------
Sep 1 10:24:02 zeus syslogd 1.4.1#2: restart.
Sep 1 10:24:17 zeus pppd[326]: rcvd [LCP EchoRep id=0x92 magic=0x9936a81f]
Sep 1 10:24:47 zeus pppd[326]: sent [LCP EchoReq id=0x93 magic=0x48b43815]
Sep 1 10:24:47 zeus pppd[326]: rcvd [LCP EchoRep id=0x93
2001 Mar 03
0
kernel & automount errors in messages log
Hello all,
I have a few strange errors in my messages log I can't fix. My system
works great, it just bugs me that I have error (or apparent errors) that
I don't know about. I get automount errors regurlarly (daily) that are
reflected in the last four lines of the log file excerpt below. My misc
and net directories are there, but I can't write to them either. The
properties say that
2003 May 26
1
Problem with bind8 and ports
Hi
When I install bind8 through ports it doesn't create the dir named 'namedb' and the needed files that it's supposed to do according to the handbook. Has anyother experienced this?
2003 Nov 06
2
ANNOUNCEMENT: NSD 1.4.0 alpha 1
This release is an alpha release. We are currently not planning to have a
1.4.0 stable release as we want to prioritize implementing DNSSEC first.
The next stable release will then be NSD 2.0.0 with DNSSEC support.
This release has some major changes: the database format is much more
compact, responses are generated on-the-fly instead of being precompiled in
the database, and the new
2004 Aug 07
1
multiple instances of NSD
I'm trying to set up a machine which will be running multiple instances
of NSD to serve different sets of zones from different interfaces. What
I'm running into is that I can't specify different PID files to refer to
on the command line.
Are there any shortcuts or do I need to go write a patch?
Any other implications of multiple instances?
--
2003 Jun 15
1
make stops in bind's compilation
Hi,
Brand-new installation of FreeBSD 4.8 + 'make world', including updating
ports, sources, crypt/secure sources and everything.
When trying to compile bind8 from ports, this is the error that get
reported:
===> Building for bind-8.3.6
Using .systype
Using .settings
/var/tmp/usr/ports/net/bind8/work/src/include
/var/tmp/usr/ports/net/bind8/work/src/include/arpa
2007 Aug 27
0
BIND 8 is EOL as of 27 August 2008 (fwd)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
For all those currently using BIND 8, please be aware of the notice below
from ISC.
Given that we have moved to BIND 9 for all of our releases from 5.x on
(and BIND 9.4.x in 7-soon-to-be-release), and given that FreeBSD 4 was the
last branch to have BIND 8, and itself is now EOL, the time has come to
say good-bye to BIND 8.
I will be
2013 Nov 26
3
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote:
>
> I made some more and more experiments beyond LBA 65535
>
> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size
> 34816)
>
> Does not work: * isolinux-5.01.bin (size 34816) * isolinux-5.10.bin
> (size 36864) * isolinux-6.00.bin (size 38912) * isolinux-6.02.bin
> (size 43008)
>
> * I just
2009 Dec 15
1
error when using multcomp and lm
I am trying to use multcomp to do a Tukey posthoc on growth increments among
genetic crosstypes.
#Fixed effect model
m1 <- lm(inc ~ 0 + Age+ Crosstype + Sex, data = Data.age)
summary(m1)
RESULTS of the model:
summary(m1)
Call:
lm(formula = inc ~ 0 + Age + Crosstype + Sex, data = Data.age)
Residuals:
Min 1Q Median 3Q Max
-0.87180 -0.34002 -0.02702 0.27710 2.17820
1998 Jun 06
21
Named update for RH 4.2 exploitable?
Someone I was speaking with this evening claimed they have installed the
latest named rpms yet they are still getting exploited daily and being
hacked. Do the latest rpm''s for the named 4.9.x stuff fix all the root
exploits or is this person just an idiot who probably has holes elsewhere in
the system?
2023 Nov 29
1
NSD 4.8.0rc1 pre-release
Hi,
NSD 4.8.0rc1 pre-release is available:
https://nlnetlabs.nl/downloads/nsd/nsd-4.8.0rc1.tar.gz
sha256 64f1da8f8163340f9d3b352ef8819e3c72c951fdd87cff55dc3b6a6b1ea27942
pgp https://nlnetlabs.nl/downloads/nsd/nsd-4.8.0rc1.tar.gz.asc
This release introduces PROXYv2 support and faster statistics gathering,
removes the database option and fixes bugs.
The proxy protocol support is an implementation
2013 Nov 26
0
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/25/2013 06:32 PM, H. Peter Anvin wrote:
> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote:
>>
>> I made some more and more experiments beyond LBA 65535
>>
>> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size
>> 34816)
>>
>> Does not work: * isolinux-5.01.bin (size 34816) * isolinux-5.10.bin
>> (size 36864) *
2013 Nov 26
3
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/26/2013 01:14 AM, H. Peter Anvin wrote:
> On 11/25/2013 06:32 PM, H. Peter Anvin wrote:
>> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote:
>>>
>>> I made some more and more experiments beyond LBA 65535
>>>
>>> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size
>>> 34816)
>>>
>>> Does not work: *
2002 Mar 06
2
Compatibility issue: OpenSSH v2.3.0p1 vs. 3.0.2: RSA keys
Hello,
I think I found a problem that should not happen:
An OpenSSH client v3.0.2 on Solaris and an OpenSSH server 2.3.0p1 on HP-
UX had a problem when authenticating:
Password login worked fine, but a password for an existing and
configured RSA1 key was never asked, the key never tried. It always
fell back to plain password authentication.
After fiddling with the client configuration
2013 Nov 26
0
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/26/2013 02:22 AM, Gerardo Exequiel Pozzi wrote:
> On 11/26/2013 01:14 AM, H. Peter Anvin wrote:
>> On 11/25/2013 06:32 PM, H. Peter Anvin wrote:
>>> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote:
>>>>
>>>> I made some more and more experiments beyond LBA 65535
>>>>
>>>> Works: * isolinux-4.07.bin (size 24574) *
2013 Oct 24
0
samba 4, joining a windows 2008R2 domain as DC. ubuntu 12.04 withsernet packages ( small howto ) W.I.P.
Hello,
?
This is a quick and dirty setup, it can be used as guideline for an "debian/ubuntu" based install
with use of the sernet samba packages. Since this was a bit hard to figure out, i'm sharing this.
?
Please correct the wrongs in this setup if you found some to make it a better and easy to read?setup.
( and please correct my typos ;-) )
?
This server wil join a windows 2008
2019 Jan 22
4
samba_dns_question
Hai,
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Rowland Penny via samba
> Verzonden: dinsdag 22 januari 2019 14:12
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] samba_dns_question
>
> On Tue, 22 Jan 2019 13:54:00 +0100
> "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote:
2019 Aug 29
0
[libvirtd] qemu_process: reset CPU affinity to all enabled CPUs, when runs in custom cpuset
Hello All,
Since 4.5.0-23.el7 version (Red Hat 7.7), when I launch pinned VM,
libvirtd reset CPU affinity to all enabled in host CPUs, if it runs in
custom cpuset.
I can't reproduce this behavior with 4.5.0-10.el7_6.12 with the same
kernel version (Red Hat 7.7).
Libvirt runs in a custom cpuset 'libvirt', where the number of
available cpus is restricted to 0,2,4,6,8.
And this
2013 Nov 26
0
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/25/2013 06:27 PM, Gerardo Exequiel Pozzi wrote:
> On 11/25/2013 04:39 PM, Thomas Schmitt wrote:
>> Hi,
>>
>> Gerardo Exequiel Pozzi wrote:
>>> Looks like there is something beyond LBA 65535 (As Mattias confirmed)
>>
>> I wanted to ask him now, whether this was already with
>> version 6.
>> But meanwhile he reported that it was 5.