Den tors 22 juli 2021 kl 13:12 skrev Arbeiter Ansgar < ansgar.arbei...@boening.com>:
> Hello Daniel, > > > > I will check if there is a Virus checker interacting. > > > > > there is sufficent time to complete the scan so you don't notice? > > it does not matter if i wait 10 seconds or 2 hours. > > relevant is that TurtoiseMerge is open while i update by script again. > > so to me it looks like Turtoise is locking some data/files and releasing > it first when i close it. > Did you check the "exclusive locking" setting as suggested by Johan Corveleyn? I think this thread should move to the TortoiseSVN support forums [1], since it it likely there is something within TortoiseMerge that keeps the connection open and it would have to be fixed there. (I'm reading that forum as well and can assist there as well). If you want to prove things, you might use Process Explorer [2] to search for which process is holding wc.db open. This information as well as any information you come up with regarding when you get the error (ie, if the error can be reproduced consistently using some specific action) will be valuable. the result of your testing batch is the following: > > > > *L:\TestProject>test_svn_lock.bat* > [...] Is L: a local drive or a network drive? TortoiseSVN explicitly advice against storing the WC in a network drive in their FAQ [3]. I have done it without any problems, but there are good reasons for this advice and YMMV. Kind regards, Daniel Sahlberg [1] https://groups.google.com/g/tortoisesvn [2] procexp.exe from http://live.sysinternals.com/ [3] https://tortoisesvn.net/faq.html#wconshare
