Hi can you give a bit more info on what you want to achieve?
why would you want to have 5? servers to update a certain file? what's the purpose of this file? maybe a safer way is that you place this file in source control. each server can do an update via the source control. and an extra server just watches this file, and on every change do what has to be done. All depends really what this file is for. with kind regards Ruben Willems On 20 April 2012 18:42, Chris <[email protected]> wrote: > I'm setting up a test farm, using ccnet/nant running on multiple machines. > I want each machine to update the SAME file on a REMOTE machine, so I don't > want simultaneous access to this file. So PC1 locks and updates the file, > then unlocks it when done. If PC2 is trying to access file while PC1 locks > it, it pends until it's unlocked. > > Or is there a better way to do this, like one ccnet/nant script running on > a central machine, that then triggers the ccnet/nant script on the test > farm to run tests? >
