Presently I have a single executable which is probably an important fact for my question about the internal HDF5 lib multi-open detection. An OS file lock could work for either case I believe.
David On Mon, Nov 16, 2015 at 9:53 AM, Miller, Mark C. <[email protected]> wrote: > Hmm. Maybe I am asking a stupid question here. . .but are you talking > about having a file opened multiple times *within* the same executable or > in different executables? > > Reason I ask is that I think the former problem is what the comment in > H5Fopen is referring to but your inquiy regarding 'locking' seems to apply > to the latter case. > > Mark > > > From: Hdf-forum <[email protected]> on behalf of David > <[email protected]> > Reply-To: HDF Users Discussion List <[email protected]> > Date: Monday, November 16, 2015 9:46 AM > To: HDF Users Discussion List <[email protected]> > Subject: [Hdf-forum] Multiply Opened Files > > I found this in the reference manual about H5Fopen(): > "In some cases, such as files on a local Unix file system, the HDF5 > library can detect that a file is multiply opened and will maintain > coherent access among the file identifiers" > > Does HDF5 maintain multi-open coherent access on Windows also? > > Ideally I'd like to have the file locked so that multiple opens are not > possible but I can't figure out a way to do that on Windows. Something like > the flock() method for Unix I've seen on this forum would be fine but I > only see file locking available via CreateFile() in the Windows API. > > - David > > > _______________________________________________ > Hdf-forum is for HDF software users discussion. > [email protected] > http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org > Twitter: https://twitter.com/hdf5 >
_______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org Twitter: https://twitter.com/hdf5
