Hey List. This is off topic, but I noticed the list has been quiet!! Trying to get different thoughts on how to approach an issue. I've got a situation, where I'm going to have a shared nfs, with a bunch of files.. I'm going to have multiple client boxes/(vms) with each client, running apps that access the files on the main nfs. The idea, is that a clientApp, on a given clientVM will access a file on the nfs, and then the nfs file is no long used. The goal is to rip through/process the nfs files as fast as possible, in a simple manner. clientVM1 clientApp1 clientVM2 clientApp2 clientVM3 clientApp3 . . clientVMN clientAppN nfsShare dataFiles... The process can't have the same data file operated on by multiple clientApps. I've thought of having a "pid" file on the nfs, where each clientApp would reset/lock/use the pidFile to then get/use/delete the file as required, but this seems tb slow.. but doable. Surprisingly, in looking around, haven't come up with anything that appears to be really better. (I've also thought of setting up a "webservice" kind of situation, where clients would get the "file/data" from a webservice, and the webservice, would interface with the nfs dir.. but this would be overkill!) Any thoughts/comments? Thanks _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
