[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Enforcing Quotas for Repositories

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-11-04 00:19:06 CET

On Nov 3, 2005, at 22:53, Mark Shead wrote:

> What is the best way to handle quotas in Subversion? Basically I'd
> like
> to provide repositories for several different teams, but I want to
> make
> sure that they can't fill the entire filesystem accidentally. The
> system would be using webdav.
> Here are the things I've thought of so far, but I'm assuming there may
> be a better way that I'm not aware of:
> 1. Put a quota on the filesystem itself. (Might not work depending on
> how Apache was configured to run.)
> 2. Use some type of commit hook to prevent a commit from going through
> if the repository is over a certain size.
> Are there any other better ways of doing this or is there anything
> that
> already gives this functionality that I might have overlooked?

Just curious: how do you envision a quota system working?
Specifically: what is the user supposed to do if they exceed the
quota? In the quota systems I know of, the user is expected to delete
items to free up space. But by definition you can never delete
anything from a repository...

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 4 00:21:01 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.