Miva Engine 3.78 Release Notes Miva Engine 3.78, released March 2001, adds the following. Fixed Items • Fixed various bugs in MvLOCKFILE that had allowed multiple users to obtain a lock simultaneously. In addition, MvLOCKFILE should now work better over NFS, and when Windows and UNIX installations are mixed. (Also see the new 'lock' configuration directives below.) • Fixed a bug that occurred when a string containing quotation marks was passed to a function called via MvDO. • Fixed a bug in the handling of the authuserdir configuration directive that (in some configurations) had authorized all non-root users with their home directories as the Miva data directory. New Configuration Directives (Options): • lockhostname= Controls the host name that is written to the lockfile. Used if there are multiple hosts writing lockfiles to the same directory, which is possible if using NFS or some other fileserver. Each system must have a unique value for lockhostname (which almost always occurs, since the network hostnames will be different). • lockexpiration= This identifies the number of seconds old a lockfile must be before it is considered "expired" and is removed. This prevents stale lockfiles from causing subsequent processes to timeout waiting for a lock. • maxfiles= When set to a value greater than 0, this directive will control the maximum number of file handles opened by the engine (not including the handle for the executable file itself, standard input, standard output, and standard error). Scripts that need to access more than "maxfiles" files simultaneously will still execute, because the engine will create virtual file handles. The default value is 0, disabled.