From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Annyoing modified by boyd
Date: Wed, 17 Sep 2014 13:36:00 +0100 [thread overview]
Message-ID: <ac37d4f164f37b4933f4e9ac7b69a828@quintile.net> (raw)
In-Reply-To: <7e68f87031a32d7438f48cf6958d99d9@krabbe.dyndns.org>
Can you trace this a bit more into cifs?
cifs is one of mine and I use it daily without problems, though I
never migrated from sam to acme, so perhaps I just don't see your issue.
I remember that smb/cifs does have weird timestamps some of which are
only changed on 2 second boundries - though the code you show should
cope happily with that.
The server has its own timestamp which cifs reads at startup and uses that
to convert the server's localtime to utc, but I think this time is read
only once per session so that is unlikely to be the problem.
Sorry if I'am a bit vague but it was 10 years ago now, but I am happy to dig
if you can provide a bit more info.
-Steve
next prev parent reply other threads:[~2014-09-17 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 11:18 Ingo Krabbe
2014-09-17 12:36 ` Steve Simon [this message]
2014-09-18 8:14 ` Ingo Krabbe
2014-09-18 9:09 ` Steve Simon
2014-09-18 21:46 ` Winston Kodogo
2014-09-18 3:41 Winston Kodogo
2014-09-18 8:20 ` Ingo Krabbe
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=ac37d4f164f37b4933f4e9ac7b69a828@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).