Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as
clients on a 100Mb/s network. The time trial used a dummy 100Meg file
transfered from the server to the client.
I have similar experiences here. With FreeBSD-6.1 as client (using an Intel
etherexpress card at 100
Hello!
I've noticed that using fdisk against ad2 drive gives misleading diagnostics
at the end of execution (there are no mounted partitions at the drive, OS
boot device is ad0):
[EMAIL PROTECTED] uname -r
6.1-RELEASE
[EMAIL PROTECTED] mount|grep ad2
[EMAIL PROTECTED] fdisk -a ad2
***
On Mon, 3 Jul 2006, Michael Collette wrote:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80389
If you locally back out the referenced change lock_proc.c:1.18 in rpc.lockd on
the server, do things improve?
Robert N M Watson
Computer Laboratory
University of Cambridge
On Mon, Jul 03, 2006 at 03:40:01PM -0700, Michael Collette wrote:
User Freebsd wrote:
On Sat, 1 Jul 2006, Francisco Reyes wrote:
John Hay writes:
I only started to see the lockd problems when upgrading the server side
to FreeBSD 6.x and later. I had various FreeBSD clients, between 4.x
I am running 6.1 release on some systems. I have a question about the bridging
changes in if_bridge.c which were made in the stable branch. I am having a
problem bonding two heavily loaded network interfaces for IDS purposes. There
is greatly increased packets droppage when using 'ifconfig
Michel Talon wrote:
Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as
clients on a 100Mb/s network. The time trial used a dummy 100Meg file
transfered from the server to the client.
I have similar experiences here. With FreeBSD-6.1 as client (using an Intel
On Tue, 4 Jul 2006, Scott Long wrote:
For what it's worth, I recently spent a lot of time putting FreeBSD 6.1 to
the test as both an NFS client and server in a mixed OS environment. By far
and away, the biggest problems that I encountered with it were due to linux
NFS bugs. CentOS, FC, and
BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd was
never
backed out. An immediate question for people experiencing new rpc.lockd
problems with 6.x should be whether or not backing out that change helps.
So it may be relevant to say that i have kernels without IPV6
On Tue, Jul 04, 2006 at 11:04:16AM -0400, Raymond Owens wrote:
I am running 6.1 release on some systems. I have a question about the
bridging changes in if_bridge.c which were made in the stable branch.
I am having a problem bonding two heavily loaded network interfaces
for IDS purposes. There
Michel Talon wrote:
BTW, I noticed yesterday that that IPv6 support committ to rpc.lockd was never
backed out. An immediate question for people experiencing new rpc.lockd
problems with 6.x should be whether or not backing out that change helps.
So it may be relevant to say that i have
Michel Talon wrote:
Using Ubuntu as the server I connected a FreeBSD 5.4 and 6-stable box as
clients on a 100Mb/s network. The time trial used a dummy 100Meg file
transfered from the server to the client.
I have similar experiences here. With FreeBSD-6.1 as client (using an
11 matches
Mail list logo
