On Feb 27, 2:39pm, "Franklin R. Jones" wrote:
} Subject: Re: Returned mail: unknown mailer error 139
} Re:
}
}
} After beating on this all day. I've discovered that the
} directory that is specified in the majordomo.cf file as `homedir' has
} to be world writable as the temp lock files are pointing at this
} directory. . . once this is done, the error goes away, and function
} seems normal. (I haevn't actually built a list as of yet.)
}
[stuff deleted for brevity]
} Is this the way this is supposed to run? please don't say yes.
}
No, it's nessary for it be that way. My majordomo
home directory is *NOT* world writeable, it's not even writable
by majordomo or daemon.
The key for this particular problem is where majordomo
logs. If majordomo is unable to create a lock file it
logs this event, unfortunately if the it cannot create
the lock file for the log file you will get into an
infinite loop.
If you look in the majordomo.cf you will probably
find a line that says:
$log = "$homedir/Log";
I personally use
$log = "/var/majordomo/logs/log";
In my case /var/majordomo/logs *is* writeable by the user
that the wrapper program is setuid to.
Other directories such as $listdir will also need to be
writeable to the effective user of the wrapper program.
}-- End of excerpt from "Franklin R. Jones"
arnold
|
|
