"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