Jason Witherspoon wrote:
>
> Hi all--
>
> Okay, so now I'm getting the following digest error:
>
> MAJORDOMO WARNING (mj_digest)!!
>
> Failed to open temp file
> '/usr/local/majordomo/lists/kozmigroov-digest.config.out', it exists
It looks like majordomo is trying to create a file that already exists.
What I don't understand is, why is majordomo trying to create a config
file? Didn't you or webmin create one when the digest was created?
>
> That's it-- couldn't find anything about it in the Log, but I just
> scanned through it. And yes, it does exist, a little 13k file w/a
> lot of preferences in it.
>
> I should mention that I created the digest list using Webmin 0.80--
>
> The only side effect seems to be that the second digest was issued
> w/the same number as the first; ie, 'V1 #1' in the 'Subject' header.
> Otherwise, the content/timing of the digest list was fine.
>
> Any clues? I guess I should just reconfigure the digest list by
> hand, but I was hoping someone might have some ideas before I rammed
> my soft grey matter against that wall--
I would be interested in seeing what webmin considers to be a digest.
What did it create for aliases? What files in the majordomo heirarchy
did it create? What permissions and ownerships did it assume were
correct for these new files? Did it make changes to any existing
aliases from the non-digest version of the list's aliases?
Dan Liston
Follow-Ups:
References:
|
|
