Hi. I set up Windows Batch files to run an update command on different
repositories that we're using. I then run the batch files through Scheduled
Tasks to have the update happen at 4am when no one's at work. It seems to
work fine in most cases, but I'm running into two specific problems:
For one of the repositories (the largest one I work with, if it matters), the
update process always skips. I can't find any documentation anywhere
mentioning this happening, or the conditions, so I'm not sure exactly what's
going on with that. Also, it's only skipping with that batch file on one
specific machine, other machines run that batch file and it updates fine.
Does anyone out there know why it would do that, and what I have to do to stop
it from skipping?
The second problem is that for a different repository, the batch update always
fails. It will say that a file is locked and I need to run the cleanup
command. I can run cleanup and update afterwards, but if I run the batch file
again, it'll give me the same error. The file that it claims is locked
differs between attempts, and it happens on every machine I've tried to run
the batch on. Does anyone have any intuition as to what is up with this?
Thanks for your help,
- Andy Maurer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Jul 24 21:45:15 2006