Further information on the following posting -- on checking the system
logfile I find that there are massive numbers of errors associated with
too many file handles. These correlate with Majordomo activity.
This is a busy list, up to 100 new subscriptions per day, and I feel
I've opened a real Pandora's box. I'll try to find someone else to take
over the list or some other software, but the present situation is
proving a real disaster. I can't serve the list and my workstation is
really getting clogged by all the activity.
>I've just set up a new list and although it is just like all the other
>lists I've got running, same permissions and all, it isn't functioning
>properly. Some subscriptions are being processed OK, but I keep on
>running into problems associated with shlock.pl that generate pages of
>the following sort of error message:
>trying lock "/usr/local/majordomo/Lists/L.fish-ecology" for pid 10495
>temporary filename "/usr/local/majordomo/Lists/.locks/shlock.10495"
>lock "/usr/local/majordomo/Lists/L.fish-ecology" already exists
>checking extant lock "/usr/local/majordomo/Lists/L.fish-ecology"
>process 10403 is extant lock is valid
>I suspect that there is too much traffic for the locking mechanism to
>handle, since sometimes a subscription attempt bounces but then the same
>message, when re-sent, is processed OK.
>This is proving a real headache, since I set the system up for a chap in
>Spain and he is baffled by all the error messages. Any help would be
Bill Silvert at the Bedford Institute of Oceanography
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2
InterNet Address: silvert @
(the address bill @
ca is only for mailing lists)