From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Thu, 18 Sep 2014 15:41:31 +1200 Message-ID: From: Winston Kodogo To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11347f46a3db8105034ec278 Subject: Re: [9fans] Annyoing modified by boyd Topicbox-Message-UUID: 16c97550-ead9-11e9-9d60-3106f5b1d025 --001a11347f46a3db8105034ec278 Content-Type: text/plain; charset=UTF-8 "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 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+1mtime){ > 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 > > > > --001a11347f46a3db8105034ec278 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
"FILE modified by boyd since last read" strikes = me as more useful than most error messages I see these days. My only questi= on is what particular weapon Boyd would have used to "modify" the= file.

On 17 S= eptember 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 c= onverges to always, get "FILE modified by boyd since last read" w= hen 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

=C2=A0 =C2=A0 =C2=A0 =C2=A0 if(d!=3Dnil && runeeq(namer, nname, f-&= gt;name, f->nname)){
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /* f->mtime+1 be= cause when talking over NFS it's often off by a second */
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if(f->dev!=3Dd-&= gt;dev || f->qidpath!=3Dd->qid.path || f->mtime+1<d->mtime){=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 f->dev =3D d->dev;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 f->qidpath =3D d->qid.path;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 f->mtime =3D d->mtime;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 if(f->unread)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 warning(nil, "%s not written; f= ile already exists\n", name);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 else
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 warning(nil, "%s modified%s%s s= ince last read\n", name, d->muid[0]?" by ":"", = d->muid);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 goto Rescue1;
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 }
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }

Hmm, possibly this is another time quirk, like that one from NFS. Does anyo= ne know a good solution to that problem?

Regards
ikrabbe




--001a11347f46a3db8105034ec278--