From: Nicolas Brainez <nb@many.be>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Performance problem
Date: 13 May 2002 17:34:24 +0200 [thread overview]
Message-ID: <1021304064.27739.29.camel@nb> (raw)
In-Reply-To: <shs3cwwqdpv.fsf@charged.uio.no>
On Mon, 2002-05-13 at 17:17, Trond Myklebust wrote:
> >>>>> " " == Nicolas Brainez <nb@many.be> writes:
>
> > Hello, I have an nfs server who exports some backup directories
> > for the lan's users, it's a new install.
>
> > First I would like say that's not an hardware problem, because
> > we have no problem to use appletalk, ftp, ...
>
> I'll bet you it is. Have you tried using a different network card + driver?
Nope, I've not another network card, and i've absolutely no problem with
others protocols like appletalk and ftp, I can't believe it's an
hardware problem in these conditions.
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-05-13 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 15:10 Performance problem Nicolas Brainez
2002-05-13 15:17 ` Trond Myklebust
2002-05-13 15:34 ` Nicolas Brainez [this message]
2002-05-14 6:41 ` Trond Myklebust
2002-05-13 16:35 ` David B. Ritch
2002-05-13 16:48 ` Greg Lindahl
[not found] <62D26CC4CB1CD3118EAA00805FBB65FA0B8B905E@perm01.woodside.com.au>
2002-05-15 8:46 ` Nicolas Brainez
2002-05-15 17:42 ` Greg Lindahl
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 13:33 Gregor Pavlin
2002-04-22 14:23 ` Joseph Bueno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1021304064.27739.29.camel@nb \
--to=nb@many.be \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.