andy.glew@amd.com wrote:
> You say "don't do that".
>
> That's easy when I am the sysadmin, e.g. of my systems at home.
>
> It's hard when I am not the sysadmin - e.g. when my project
> is using diskspace that has been granted us by corporate IT,
> or if I want to do something like run a Subversion repository
> on some web hosting site. I have almost no control over the
> logical arrangement of filesystems.
> It's highly unlikely that anyone else is running
> Berkeley DB tools against my data.
> But it's highly likely that they are running filesystem
> read-only indexing tools, backup tools, snapshot tools, etc.
> on the filesystem that holds my data.
>
> My question is whether such filesystem read-only access can
> screw up a Subversion repository. As I think about it,
> I doubt that there is a problem. But I was initially scared
> by some of the language in the book.
As long as you're not expecting to actually be able to use the backup of
the Subversion repository, I don't see how it could hurt anything,
assuming you're actually opening it read only. That said, when someone
says they're 'backing something up', I tend to assume you actually want
to use the backup for something other than wasting space. If that's not
the case, then sure, you should be fine.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 21:23:11 2004