:> Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP.
:> AMD defaults to tcp.
:
:I made a commit to -STABLE a few weeks ago (but not -CURRENT) that should
:have made v3/udp the default.
:
:--
:-- David(obr...@nuxi.com -or- obr...@freebsd.org)
Ah, cool. I'll bet the aut
> Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP.
> AMD defaults to tcp.
I made a commit to -STABLE a few weeks ago (but not -CURRENT) that should
have made v3/udp the default.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord..
:Symptoms are the following: We upgraded a perfectly running 2.2.7 client
:to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging
:for ten, twenty seconds, even five minutes or more.
:
:Adding the NFSv2 compatibility option to the AMD tables solved the
:problem.
:
:Gerald
:--
:
On Thu, 22 Apr 1999 00:51:03 +0200, Gerald Pfeifer wrote:
> Symptoms are the following: We upgraded a perfectly running 2.2.7 client
> to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging
> for ten, twenty seconds, even five minutes or more.
>
> Adding the NFSv2 compatibil
I'm only subscribed to freebsd-stable, so I missed the original thread,
but reading the lines below, a question arises:
On Wed, 21 Apr 1999, Matthew Dillon wrote:
> Well, you already see a lot of the pure bug fixes being backported.
> What you don't see in -stable are the bug fixes that also depen
