From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul C Lustgarten To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Message-Id: <20010519234657.4A6FC199C1@mail.cse.psu.edu> Subject: [9fans] Re: tracking file modifiers (was: home, end ^h^j^k^l) Date: Sat, 19 May 2001 19:46:55 -0400 Topicbox-Message-UUID: a2f1333e-eac9-11e9-9e20-41e7f4b1d025 At 10:14 AM 5/19/2001 -0400, rob pike wrote: > The -m flag reports the muid (modifier uid) of the file, as reported > in the new 9P protocol. This is the person who most recently modified > the file, instead of the person who created it. If I had a collection of projects using Plan 9, and wanted to bill back file store (WORM) usage to those projects, would this muid provide enough information to do so? I'm willing to assume that each user is a member of only one project. And I don't care about daily cache usage - I just want to allocate responsibility for consumption of the blocks on the WORM, while having all the other benefits of sharing that WORM amongst those projects. I'm imagining that the muid would make it easy to handle the simple case of files that are modified by just a single user (like me editing my lib/profile). What about files written by multiple users (e.g., several developers editing a shared project file, all within the same day), or append-only (log, mailbox) files that have been extended by several different users (again, within a single day)? Also, on the topic of managing WORM consumption, is there some way to protect the WORM from excess consumption, using the new muid or otherwise? I'm thinking of scenarios such as programming mistakes where a user accidentally writes a bunch of stuff that they didn't intend and don't notice, or where they do something stupid like copying over the entire project's source tree in order to make a personal build with a couple of modified files. I keep thinking of being able to impose per-user quotas that would be enforced by the system itself (as part of the nightly dumps?), as a safety measure complementing the economic incentive created by charging the projects for what their users do consume.