That's majordomo's equivalent of a kernel panic or other fatal error.
That looks like it doesn't have permission to write to the directory where
it's trying to create the lock file.
Check to see if the majordomo user (usually majodomo) can write to the
directory in question then have your ISP check to see if the wrapper
script is still setuid root.
On Fri, 15 Jan 1999, Miryam Williamson wrote:
> Date: Fri, 15 Jan 1999 11:23:38 -0500
> From: Miryam Williamson <mwilliamson@reporters.net>
> To: majordomo-users@GreatCircle.COM
> Subject: MAJORDOMO WARNING (mj_resend)
>
> MY ISP, who hosts a majordomo list called siblist for me, doesn't know what
> this means. Nor do I. Can anyone help?
>
> Interestingly, I own two other majordomo lists on the same server and
> neither produces this error. I've compared the list.config files and can't
> see any differences other than the relevant list names.
>
> >To: owner-siblist
> >Subject: MAJORDOMO WARNING (mj_resend)
> >Reply-To: owner-siblist
> >
> >--
> >
> >MAJORDOMO WARNING (mj_resend)!!
> >
> >shlock: open('/home/users/majordom/lists/siblist.config.LOCK'): No such file
> >or directory
> >
>
> ~~~~~
> Miryam Williamson
> <mwilliamson@reporters.net> / <http://www.shaysnet.com/~wmson/>
>
--
------------------------------------------------------------------------------
stick@physis.viper.net Chris MacLeod
Web Systems Administrator www.miscellaneous.net
With blue, uncertain, stumbling buzz,
Between the light and me,
And then the windows failed, and then
I could not see to see.
-Emily Dickenson "I Heard A Fly Buzz When I Died"
------------------------------------------------------------------------------
"Beware the penguins..." -Morphy
GNUpgp Public key Available - finger physis@miscellaneous.net
References:
|
|
