… been loaded This will help avoid confusion in cases where the NFS server is busy and it takes a while to get a response from it. I'm not happy about the solution I had to use. I filed rfe13690 in hopes of a better future solution.
Got rid of all warnings when building hammernfs on Mac OS X. Also: Makefile: Clean hammernfs in 'clean' target. Added 'tags' target. hammernfs.c: Use strerror() to expand error codes in lookup2 and lookup3. This assumes that the returned code is the same as the Unix errno, which is generally true. One of these I'll need to make a mapping function.
Fix from John Peterson via github. Manually added from pull request: #7
So it can at least be modified by more experienced users. Also, the main server and configuration now share the definitions of all configuration variables. They're in config-defs.cl. Renamed loadem.cl to load.cl (since load.cl is sort of a standard name for loading a project).
Prior to this commit, hammernfs used time() to determine if the test interval had completed. time() only has one second resolution. Changed to use gettimeofday which has (potentially) microsecond resolution. Actual resolution will depend on the OS but it'll surely be better than one second. Added the number of reads to the report.
symlink-p: Handle the case where we can get the file attributes but not open the file. Just return nil if that happens. unicode-stat: Directories marked read-only aren't necessarily read-only, so handle this by reporting directories as always writeable.