I have seen this on occassion too, but not in quite some time myself.
I think this might have something to do with permissions or ownership
of the lists directory or config file. This lock should only happen
(maybe I should go read the script files again before saying this)
when you are writing a new config for the list, or a digest is being
created which needs to update the config for the next volume/issue
number to be used.
config_parse.pl, digest, and majordomo all have reference to config.LOCK,
archive2.pl, config_parse.pl, majordomo, and request-answer all have
calls to shlock.pl. Interesting that the WARNING looks like it came
from resend.
Check your $listdir for any files with .LOCK extensions or shlock
basenames. I have just deleted these when I found them, but it may
be safer to make sure sendmail/majordomo are not active when you
attempt this.
Dan Liston
Ed Kasky wrote:
>
> MD 1.94.5 on RH 6.1
>
> This just popped up this morning and is a new one on me. I couldn't find
> any reference to the specific error in the faq or the archives...
>
> resend[13343] {listname} WARNING
> shlock: link('/usr/local/majordomo/lists/shlock.13343',
> '/usr/local/majordomo/lists/listname.config.LOCK'): No such file or directory
>
> A decent amount of mail goes through this particular list with no problem.
>
> Other mail has since gone through the same list since then. Is is
> something I should be concerned about?
Follow-Ups:
References:
|
|
