From: Ingo Krabbe <ikrabbe.ask@gmail.com>
To: <9fans@9fans.net>
Subject: Re: [9fans] Annyoing modified by boyd
Date: Thu, 18 Sep 2014 10:20:54 +0200 [thread overview]
Message-ID: <9ead16deb8bf1dd6d0bc7904bb2f88e8@krabbe.dyndns.org> (raw)
In-Reply-To: <CAFiGbxhDScrjczwvvdmF=NAeWSbGn05g54EJVPN-7pbo9m0NAg@mail.gmail.com>
> "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.
Hey Winston,
I agree that the message itself would be extremely useful if it would be reported correctly. But acutally when its just me who modifies a remote file with acme in a editing session, I get these modified by boyd warnings and I will get the same warning if someone else had modified the file, in the end this really useful message gets useless, as most times it is wrong and gets auto-ignored by the chair-to-keyboard-interface.
FYI: boyd is the unknown modifiying user of any file on cifs, who is a friend of bill and trog. I always think of boyd to be the younger brother of void.
Regards
Ingo Krabbe
> 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
>>
>>
>>
>>
next prev parent reply other threads:[~2014-09-18 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 3:41 Winston Kodogo
2014-09-18 8:20 ` Ingo Krabbe [this message]
-- 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=9ead16deb8bf1dd6d0bc7904bb2f88e8@krabbe.dyndns.org \
--to=ikrabbe.ask@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).