On Jan 11, 2012, at 02:17, Tom wrote: > I have a subversion repo exposed through mod_dav_svn and the option > "SVNAutoversioning on" and am using fusefs with davfs2 to mount the repo on > my linux desktop fedora 15. > > This usually allows webDAV clients to make changes to files without a > checkout-edit-commit cycle, and this works well for some subset of the > repository for convenience. In this instance I am using subversion for > centralized versioning rather than source control. > > The server intermittently zeroes out the files, either geany/gedit offers a > reload (which I have learned is a no-no) and the file reloaded is empty. [snip]
Well something zeroes the files. I don't think it's the server. When this happens, is the last good version of the file, before it was zeroed, still in the repository history? I mean: if the file contains "A" and you save it and all is well (file contains "A" in the repository), and then you change the file contents to "B" and save again and then notice the file has been zeroed, does the file in the repository contain "B" or still "A"? Different editors probably employ different methods of saving files. Some might write a temporary file, then move it on top of the old file. Some might just zero the original file, then write the new one. Perhaps you would see different behavior (perhaps no failure) if you used a different editor.
