From: Winston Kodogo <kodogo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Annyoing modified by boyd
Date: Thu, 18 Sep 2014 15:41:31 +1200 [thread overview]
Message-ID: <CAFiGbxhDScrjczwvvdmF=NAeWSbGn05g54EJVPN-7pbo9m0NAg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
"FILE modified by boyd since last read" strikes me as more useful than most
error messages I see these days. My only question is what particular weapon
Boyd would have used to "modify" the file.
On 17 September 2014 23:18, Ingo Krabbe <ikrabbe.ask@gmail.com> wrote:
> Hey,
>
> using legacy bell-labs plan9 (I don't know the others), I often, that
> converges to always, get "FILE modified by boyd since last read" when
> editing a file on a cifs share with acme.
>
> The cifs main.c defines "boyd" as the "modifying user" (muid) in I2D and
> V2D, which are from fs.stat.
>
> From /sys/src/cmd/acme/exec.c:/putfile/+14
>
> if(d!=nil && runeeq(namer, nname, f->name, f->nname)){
> /* f->mtime+1 because when talking over NFS it's often off
> by a second */
> if(f->dev!=d->dev || f->qidpath!=d->qid.path ||
> f->mtime+1<d->mtime){
> f->dev = d->dev;
> f->qidpath = d->qid.path;
> f->mtime = d->mtime;
> if(f->unread)
> warning(nil, "%s not written; file already
> exists\n", name);
> else
> warning(nil, "%s modified%s%s since last
> read\n", name, d->muid[0]?" by ":"", d->muid);
> goto Rescue1;
> }
> }
>
> Hmm, possibly this is another time quirk, like that one from NFS. Does
> anyone know a good solution to that problem?
>
> Regards
> ikrabbe
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2226 bytes --]
next reply other threads:[~2014-09-18 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 3:41 Winston Kodogo [this message]
2014-09-18 8:20 ` Ingo Krabbe
-- strict thread matches above, loose matches on Subject: below --
2014-09-17 11:18 Ingo Krabbe
2014-09-17 12:36 ` Steve Simon
2014-09-18 8:14 ` Ingo Krabbe
2014-09-18 9:09 ` Steve Simon
2014-09-18 21:46 ` Winston Kodogo
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='CAFiGbxhDScrjczwvvdmF=NAeWSbGn05g54EJVPN-7pbo9m0NAg@mail.gmail.com' \
--to=kodogo@gmail.com \
--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).