diff options
Diffstat (limited to 'release_docs')
| -rw-r--r-- | release_docs/INSTALL_parallel | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/release_docs/INSTALL_parallel b/release_docs/INSTALL_parallel index 6f60165..e5be615 100644 --- a/release_docs/INSTALL_parallel +++ b/release_docs/INSTALL_parallel @@ -23,8 +23,7 @@ with your system support staff of information how to compile an MPI program, how to run an MPI application, and how to access the parallel file system. There are sample MPI-IO C and Fortran programs in the appendix section of "Sample programs". You can use them to run simple tests of your MPI compilers -and the parallel file system. Also, the t_posix_compliant test in testpar -verifies if the file system is POSIX compliant. +and the parallel file system. 1.2. Further Help @@ -322,11 +321,6 @@ non-zero code. Failure to support file size greater than 2GB is not a fatal error for HDF5 because HDF5 can use other file-drivers such as families of files to bypass the file size limit. -The t_posix_compliant tests if the file system is POSIX compliant when POSIX -and MPI IO APIs are used. This is for information only and it always exits -with 0 even when non-compliance errors have occurred. This is to prevent -the test from aborting the remaining parallel HDF5 tests unnecessarily. - The t_cache does many small sized I/O requests and may not run well in a slow file system such as NFS disk. If it takes a long time to run it, try set the environment variable $HDF5_PARAPREFIX to a file system more suitable |