Hi!
After installing Majordomo v1.94 into one of our computers, we've
encountered the following problem. When Majordomo is unable to
create a shlock file (lets say a target directory doesn't exist
or have wrong permissions), it goes into apparent infinite loop,
bombarding Majordomo owner with steady stream of messages such as:
WARNING open of temp file /usr/local/majordomo/digests/foo/shlock.12652 failed
The only way to break the loop is to kill the offending process such as:
majordom 12652 1.2 8.2 1016 1328 ?? S 1:17PM 0:10.22 /usr/local/bin
/perl /usr/local/majordomo/digest -m -C -l foo foo-outgoing (perl4.036)
The reason for Majordomo's unability to open shlock file in the above
example is that foo list owner send "mkdigest foo PASSWD" instead of
"mkdigest foo-digest PASSWD" and while /usr/local/majordomo/digests/foo-digest
were in existence, /usr/local/majordomo/digests/foo weren't. Admittedly,
foo list owner made a mistake, but it shouldn't have resulted in the
non-ending stream of messages. Is there something we can do fix that?
Thanks!
[Please Cc your responses (if any) to me -- mikhail@klm.com]
--mikhail
|
|
