We have had majordomo running fine for about 6 months now. Then, we
changed some of the permissions so a user could do some work on the
majordomo directories. The wrapper has uid daemon and gid majordom, all
the scripts are 775 majordom:majordom, all dirs the same, and all files
664 majordom:majordom, but I get gobs of ABORT and permission denied
messages every time majordomo tries to do something.
If this is a clue, all the digest files that digest creates are
daemon:other instead of majordom:majordom. Is there anything I am missing???
James Eagan, who can't seem to find the answer anywhere...
Nagilum@branson.org
|
|
