I installed 1.94 last weekend over a copy of 1.93. After installing Perl
5.003, MD1.94 worked like a champ (I'll provide a blow-by-blow discussion
in a future post).
However, I got two identical messages from majordomo each on two different
days:
WARNING ()
shlock: open("/usr/local/majordomo/L.Log"): No such file or directory
The messages are produced the same time the cron job runs the digesting
for the 6 lists we host; I could not find any commonality as to which
list or which digest the warnings were related to. I grepped "L.Log" in
all of the MD directories, trying to find if I had a typo or something else,
to no avail.
I then found this (repeated four times--the same number of times I've
gotten the message) in ~/majordomo/tmp/majordomo.debug:
WARNING ()
shlock: open("/usr/local/majordomo/L.Log"): No such file or directory
WARNING shlock: open("/usr/local/majordomo/L.Log"): No such file or
directory at /usr/local/majordomo/majordomo.pl line 263.
Line 263 in majordomo.pl is:
warn("WARNING ", @_);
So, that doesn't tell me anything, but I'm not a programmer, anyway, so
don't let that fool you.
As best I can tell, MD locks the Log file, making it L.Log, and then tries
to lock it again....?
Any thoughts?
Jim
__________________________________________________________________
Jim Dawson jdawson@navi.net
GCN Communications, Inc. http://www.navi.net
2305 NW Kearney St. Ste. 239 voice: +1.503.531.1978
Portland, Or 97210 USA fax: +1.503.531.1979
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Follow-Ups:
|
|
