[ Bill writes: ]
> One thing that I tought about doing on my production list after the testing
> had ended on the test list (bad, bad boy) is to soft link the config file
> for the digest list to the config file for the "regular" list; in other
> words, I could not see a reason why the regular and the digest lists should
> have different config files, so I made them be one and the same (of course,
> via a link, so there are actually two differently-named files out there).
In a word, locking. One Mj request locks "alist.config" and another
locks "alist-digest.config", which is actually a symlink to
"alist.config". Since Mj locking is done via lock files, both processes
have obtained valid locks to what amounts to the same file. I suppose
if you and everyone else who might ever change the config file knows to
never, ever, ever (and then some) try to change the config file through
the symlink, you might be OK, but...