From: Frank Cusack <fcusack@fcusack.com>
To: "Mikkelborg, Kjetil" <kjetil.mikkelborg@kongsberg.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS directory caching
Date: Tue, 24 Jun 2003 03:32:58 -0700 [thread overview]
Message-ID: <20030624033258.D4036@google.com> (raw)
In-Reply-To: <75587E33AC778145AACCE1601EEABF420D496F@kda-beexc-02.kda.kongsberg.com>; from kjetil.mikkelborg@kongsberg.com on Tue, Jun 24, 2003 at 11:06:02AM +0200
On Tue, Jun 24, 2003 at 11:06:02AM +0200, Mikkelborg, Kjetil wrote:
> How is it with directory caching in standard nfs client for linux? Is it
> existent at all? And if so, is there any way I can modify its timeout
> values for spesific mountpoint?
man 5 nfs
...
> It would be nice to eliminate the issue with extensive NFS directories
> in path problem, without altering the existing PATH setting, since for
> managment reasons it is much more easier to have most of the common
> tools on a NFS volume than installed on each workstation.
For some types of software, yes. I would have disagreed until recently
(now that my site is moving away from that).
/fc
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-06-24 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 9:06 NFS directory caching Mikkelborg, Kjetil
2003-06-24 10:32 ` Frank Cusack [this message]
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=20030624033258.D4036@google.com \
--to=fcusack@fcusack.com \
--cc=kjetil.mikkelborg@kongsberg.com \
--cc=nfs@lists.sourceforge.net \
/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.