All,

Since this is my first post, I would like to say how much I like Fossil. I 
discovered Fossil about 4 month ago, did some initial testing and recommended 
it for use on our many small projects. It is now used on 6 different projects.

The other day one of our developers accidentally checked in a large zip file of 
about 160 meg. After that the repository could not be cloned successfully over 
the network. I ran the following scenario as a test using an XP 64 machine with 
Apache 2 running Fossil as a CGI. I used the latest windows fossil.exe from the 
downloads.

I created a new repository and began filling it with items. I was able to clone 
this repository successfully till it got to about 325 meg. At that point the 
client attempting the clone reaches 98.7% complete and up pops the windows 
dialog saying "fossil.exe has encountered a problem and needs to close". If I 
work with the repository locally I can still use it and continue to add 
artifacts. The network clone simply will not complete successfully.

I tested an older fossil.exe from Feb. by creating yet another repository and 
using "fossil.exe server repo.fossil" as the server. The clone does not 
complete in the this scenario either.

Is there something about the networking I am missing? What can I do to help 
find the problem? Network Cloning is pretty key to our operation.

Thanks,
Tony Jefferson





      
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to