Re: repos not accessible after log files removed (II)

Jan Hendrik wrote:
> Generally it looks like it happens faster or at least more likely when
> the repos is accessed via Apache through the LAN than via
> Apache a/o file:/// on the local disk. But I stress the "faster" and
> "more likely".
>

I don't quite understand that paragraph; are you saying that access through
http:// is more likely to cause the problem than file:// access?

> Since for me there is no pattern I can follow after about three
> working days spent on this I recalled Subversion from production to
> low level testing. That is I keep two or three private copies of
> working copies and update/commit them occasionally while doing
> production by old-fashioned synchronizing again. And give Perforce
> a second try.
>

As already pointed out, no one responded most likely because no one has had
these problems. There is likely to be something specific to your environment
that is causing problems to surface.

Are you running any sort of virus-scanner on the server? Do you have the
repository located on a FAT32 volume or an NTFS volume? Are you attempting to
use file:// access to a network mounted share? Is the repository local to the
Apache server or is it located on a mounted share?

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org