>
> Yes, I agree it's possible that you know more. But I've seen no
> evidence of that today.
>
> YOU sent an email to the Subversion users list with the subject
> "Bug? FSFS revision control"
>
> There are two things about that subject that make me pretty certain
> that what may be true about your paragraph is not true.
>
> 1) It's CLEARLY not a bug
> 2) It has NOTHING to do with FSFS per se.
>
>> Please make sure to read my statement about MS SQL Server data file
>> access; you may finally learn a thing or two about an attempt to secure
>> a working environment in an otherwise unsecure one.
>
> That was a nicely attempted rebuttal to (everyones?) response that your
> statements in your first email were half-baked at best. However, since
> Subversion is not a continuously running daemon (in most instances)
> how in the world could it keep a lock on the file?
>
> So, try this: Stop the SQL server, modify it's files, and start it again.
You don't actually need to do this.
You can (assuming you are administrator or have enough permissions) simply
use the various debug hooks to attach to it's process space and happily fart all
over it's memory mapped copy of the database, regardless of how it has it
locked.
It's really not that hard for any windows programmer to do.
Really.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 27 04:49:56 2005