wosteen Posted December 9, 2009 Share Posted December 9, 2009 If I use FileOpen with output/append on a file on a UNC share, will it be opened in shared mode? I'd like a single log file to reside on a server share, and multiple machines may run the script at the same time. They'll be writing a single transaction record to the file. Will there be any write contention from multiple users attempting to write simultaneously? Thanks! Wayne Link to comment Share on other sites More sharing options...
PsaltyDS Posted December 9, 2009 Share Posted December 9, 2009 (edited) If I use FileOpen with output/append on a file on a UNC share, will it be opened in shared mode?I'd like a single log file to reside on a server share, and multiple machines may run the script at the same time. They'll be writing a single transaction record to the file. Will there be any write contention from multiple users attempting to write simultaneously?Thanks!WayneThere's no such thing as "write simultaneously". You would have to implement your own file locking mechanism. Or you could put it on any generic database service, or purpose built logging service ala SysLog. P.S. Maybe an easier solution for AutoIt scripting is run an AutoIt-based service that monitors the folder for log transaction files, then reads, integrates, and deletes them. The reporting machines only need to write a unique transaction file for each event, with a unique naming format that guarantees they create a new file each time. Edited December 9, 2009 by PsaltyDS Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law Link to comment Share on other sites More sharing options...
wosteen Posted December 9, 2009 Author Share Posted December 9, 2009 P.S. Maybe an easier solution for AutoIt scripting is run an AutoIt-based service that monitors the folder for log transaction files, then reads, integrates, and deletes them. The reporting machines only need to write a unique transaction file for each event, with a unique naming format that guarantees they create a new file each time.Thanks Psalty. I was kind of thinking about this option myself, but had dismissed it. I think I will go with it now. Thanks for the pointer!Wayne Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now