M2H_DBFILE
and M2H_OUTDIR
environment
variables or the command-line options -dbfile
and -outdir
.
Otherwise, the current working directory is used.
NOTE: The database file must be in the same location as the archive since the
M2H_OUTDIR
variable and -outdir
option also specify the location of the
archive.
The database file contains data to update any mail threads and the resource settings when MHonArc was last invoked. This allows new messages to contain the same formatting/resource specifications as existing messages in the archive without having to re-specify the resources each time new messages are added. Resources defined in the database file override the environment variables.
NOTE: If no database file is found, MHonArc will creates a new archive.
.mhonarc.lck
", when creating/updating
an archive. The lock file insures that only one MHonArc process is
modifying an archive at any given moment. The M2H_LOCKTRIES
environment variable allows you to control how long a given MHonArc
process will wait if an archive is currently locked. If MHonArc can not lock
the archive after the specified number of tries, MHonArc will exit.
SIGABRT
, SIGHUP
, SIGINT
, SIGQUIT
, SIGPIPE
,
SIGTERM
. Possible archive corruption can still occur if a SIGKILL
signal
is received since SIGKILL
s are uncatchable. A SIGKILL
will also prevent
MHonArc from deleting the lock file. This will prevent other invocations of
MHonArc from updating the archive. If this occurs, you need to manually
remove the lock file.
The comment delcarations look like the following:
<!--X-Body-Begin--> <!--X-User-Header--> <!--X-User-Header-End--> <!--X-TopPNI--> ...
-add
option.
MSGSEP
resource gives flexibility in processing mailbox style
files.