From: Martin Harriss <martin@Princeton.EDU>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Worm consumption (was: Re: tracking file modifiers)
Date: Sat, 19 May 2001 23:12:02 -0400 [thread overview]
Message-ID: <3B073602.5B439C05@princeton.edu> (raw)
In-Reply-To: <20010519234657.4A6FC199C1@mail.cse.psu.edu>
Paul C Lustgarten wrote:
>
> 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.
You might consider having a separate "scratch" file system not backed up by
a WORM. Anything transient you put in scratch. Anything precious you put
in the WORMed file system.
Martin
next prev parent reply other threads:[~2001-05-20 3:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-19 23:46 [9fans] Re: tracking file modifiers (was: home, end ^h^j^k^l) Paul C Lustgarten
2001-05-20 0:02 ` Boyd Roberts
2001-05-20 3:12 ` Martin Harriss [this message]
2001-05-20 3:17 ` [9fans] Worm consumption (was: Re: tracking file modifiers) Boyd Roberts
2001-05-20 4:44 Paul C Lustgarten
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=3B073602.5B439C05@princeton.edu \
--to=martin@princeton.edu \
--cc=9fans@cse.psu.edu \
/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).