Normally, an existing lock file implies that another MHonArc process is currently using the archive, and other MHonArc processes will wait awhile to see if the archive will be unlocked. However, there are times when a lock file exists, but no MHonArc process is modifying the archive. This can occur if MHonArc is abnormally terminated. Warnings Warning messages denote some undesired event occurred, but the event is not severe enough to cause program termination. The message is given the current date if no date is found.
Problems can arise if the database file changes in format from different version of MHonArc .
See the release notes of the MHonArc distribution if changes in the databse format will effect older archives. This message can occur if outdir permissions changed during MHonArc execution, the existing dbfile is read-only, or the file system is full. This warning can be severe because no future add operations can be performed to the archive. Make sure footer exists, and is readable by you. Make sure header exists, and is readable by you.