mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ioe-lkml@rameria.de>
To: linux-kernel@vger.kernel.org
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, joe.korty@ccur.com
Subject: Re: [BUG] NFS no longer updates file modification times appropriately
Date: Fri, 4 Jun 2004 05:25:38 +0200	[thread overview]
Message-ID: <200406040525.40972.ioe-lkml@rameria.de> (raw)
In-Reply-To: <1086297112.3659.3.camel@lade.trondhjem.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

On Thursday 03 June 2004 23:11, Trond Myklebust wrote:
> ...and no - we do not update timestamps on the client side when we cache
> the write, 'cos NFS does not provide any device for ensuring that clocks
> on client and server are synchronized.

Could you make this an option? The device ensuring this is the an admin
with a clue, who configures NTP or similiar in his network.

If unsure you could at least disable it by default.


Regards

Ingo Oeser

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAv+uyU56oYWuOrkARAvbCAJ0cG2HI4ScMAR8R8Iie5NN1FerGoQCdExHm
RF4Y/hZoKf4DuTr1w9lLPKY=
=EmI4
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-06-05 12:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 20:28 Joe Korty
2004-06-03 21:11 ` Trond Myklebust
2004-06-04  3:25   ` Ingo Oeser [this message]
2004-06-06 19:17     ` Trond Myklebust
2004-06-04 13:23   ` Joe Korty
2004-06-04 23:08     ` Trond Myklebust
2004-06-04 23:24       ` Stephen Hemminger
2004-06-04 23:37         ` Trond Myklebust
2004-06-07 15:21   ` Joe Korty
2004-06-07 15:51     ` Trond Myklebust
2004-06-07 16:13       ` Joe Korty
2004-06-07 16:20         ` Trond Myklebust
2004-06-07 16:39           ` Joe Korty
2004-06-07 16:53             ` Trond Myklebust
2004-06-07 17:01               ` Trond Myklebust

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=200406040525.40972.ioe-lkml@rameria.de \
    --to=ioe-lkml@rameria.de \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®