Is there a sysctl variable, or a quick method to determine if ipv6 is
enabled in the kernel? e.g. How do I test for the prescence of ipv6 in
a script or at the commandline?
Thanks,
Billy
___
freebsd-stable@freebsd.org mailing list
On Tue, Jul 05, 2005 at 12:17:40AM +0200, K?vesd?n G?bor wrote:
The bind user has the uid 55. I've added a rule for it, as You can see,
but it doesn't help. I get this error with the ruleset can be seen
above, and also without any rules. But apache works. It can change to
the www user.
On Tue, Jul 05, 2005 at 01:17:41AM -0500, Billy Newsom wrote:
Is there a sysctl variable, or a quick method to determine if ipv6 is
enabled in the kernel? e.g. How do I test for the prescence of ipv6 in
a script or at the commandline?
You could check for the existance of the net.inet6
Hi
Ever since i upgraded to 5.4-RELEASE-p3 i get these entries in
/var/log/messages once in a while :
kernel: bge0: watchdog timeout -- resetting
Shall i worry? ;)
U.
___
freebsd-stable@freebsd.org mailing list
On Tue, Jul 05, 2005 at 01:17:41AM -0500, Billy Newsom wrote:
Is there a sysctl variable, or a quick method to determine if ipv6 is
enabled in the kernel? e.g. How do I test for the prescence of ipv6 in
a script or at the commandline?
You could use ifconfig together with the loopback
I've only ever had that message, on network cards that were about to die.
Uzi Klein wrote:
Hi
Ever since i upgraded to 5.4-RELEASE-p3 i get these entries in
/var/log/messages once in a while :
kernel: bge0: watchdog timeout -- resetting
Shall i worry? ;)
U.
Chris Phillips wrote:
I've only ever had that message, on network cards that were about to die.
The machine is a new HP DL380-G4
I doubt the card is dying (even tho its the easy way out for me)
Uzi Klein wrote:
Hi
Ever since i upgraded to 5.4-RELEASE-p3 i get these entries in
Uzi Klein a écrit :
Chris Phillips wrote:
I've only ever had that message, on network cards that were about to die.
The machine is a new HP DL380-G4
I doubt the card is dying (even tho its the easy way out for me)
we have 3 HP DL380-G4 with FreeBSD 5.4-RELEASE-p3 and I never seen this
on 01.07.2005 20:13 Poul-Henning Kamp said the following:
In message [EMAIL PROTECTED], Andriy Gapon writes:
I am actually OK with such situation. The problem is that the only
device created is obviously da0 i.e. there are no devices for slices
present on medium. So, when the card reader
Hi,
You (Mark Andrews) wrote:
FreeBSD's pthread_mutex_init() (isc_mutext_init()) can fail
if there is no memory. On most other OS this is not the case.
The callers to isc_mutext_init() assume that a failure is due
to a double initialision and as a result log a
David Malone wrote:
If you don't actually want to use IPv6, you could give explicit
addresses to named using the listen-on and query-source directives.
Alternatively, a kernel without IPv6 might work.
I don't have IPv6 support in the kernel. Anyway, I tried to set those
directives in
Hi all,
as you probably have noticed, the amount of mails about
problems with compiling ndis has increased in the last
four weeks.
The old way to compile ndis was to go to
/usr/src/sys/modules/if_ndis/, use ndiscvt to create a header
file containing the windows driver and to make;make install.
In message [EMAIL PROTECTED], Andriy Gapon writes:
on 01.07.2005 20:13 Poul-Henning Kamp said the following:
In message [EMAIL PROTECTED], Andriy Gapon writes:
I am actually OK with such situation. The problem is that the only
device created is obviously da0 i.e. there are no devices for
On Jul 5, 2005, at 4:02 AM, Uzi Klein wrote:
Hi
Ever since i upgraded to 5.4-RELEASE-p3 i get these entries in /var/
log/messages once in a while :
kernel: bge0: watchdog timeout -- resetting
Shall i worry? ;)
Yes, worry. I had that on my Tyan S2881 motherboard onboard NICs.
System
Gleb Smirnoff wrote:
G How often does it crash? Does debug.mpsafenet=0 increases stability?
G
G I can reproduce the crash within 60 seconds of firing off 30+ ping/arp
G -d scripts, all running in parallel.
G
G debug.mpsafenet=0 seems to have solved the problem. I'm running 100+
G instances
Hi John,
From my console:
FreeBSD 5.4-RELEASE-p2 #2: Wed Jul 6 00:01:31 CEST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MASTER
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Opteron(tm) Processor 248 (2193.76-MHz K8-class CPU)
Origin = AuthenticAMD Id = 0xf5a Stepping = 10
Recently, I added a new server to our network, using the 3Ware RAID
controller (the 9500S-4LP card) and 3x140G SATA drives ... overall, the
system works, but I'm getting a very odd behaviour that I've never seen
before ...
I have a process that run an rsync from another server to
Readily reproducable, 5.4-STABLE as of last week.
Kernel messages prior to panic (from memory):
pcm0: unregister: mixer busy
WARNING: Driver mistake: destroy_dev on 30/3
Backtrace:
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU
Scott Long wrote:
The 2020 seems to be in a pre-release phase just for SuperMicro. It's
not mentioned at all on the Adaptec website. I've been in contact with
Adaptec engineers who are preparing updates for the FreeBSD driver for
it, but it's looking unlikely that they will be done in time for
On Wednesday, 6 July 2005 at 2:31:37 +0200, Michael Nottebrock wrote:
Readily reproducable, 5.4-STABLE as of last week.
Kernel messages prior to panic (from memory):
pcm0: unregister: mixer busy
WARNING: Driver mistake: destroy_dev on 30/3
This is a phkism. It's supposed to tell the
On Tue, 5 Jul 2005 22:49, Fabian Keil wrote:
AFAIK, nobody has announced that the old way is death,
therefore I would like to know if the breakage is intentional
and if it is, if there's a technical reason why these methods
can no longer coexists.
The old way built the .sys and .inf files
On Wed, 6 Jul 2005 10:16:59 +0930
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
On Wednesday, 6 July 2005 at 2:31:37 +0200, Michael Nottebrock
wrote:
Readily reproducable, 5.4-STABLE as of last week.
Kernel messages prior to panic (from memory):
pcm0: unregister: mixer busy
On Wed, 6 Jul 2005 11:42:41 +0800
Ariff Abdullah [EMAIL PROTECTED] wrote:
On Wed, 6 Jul 2005 10:16:59 +0930
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
On Wednesday, 6 July 2005 at 2:31:37 +0200, Michael Nottebrock
wrote:
Readily reproducable, 5.4-STABLE as of last week.
Hi,
Can anybody tell me what benefit for building a tap
pseudo ethernet device driver for some sort of network
communication? Why not directly communicate thru a
real ethernet device driver like fxp0, xl0, etc.
Thanks
Sam
24 matches
Mail list logo
