On 8/7/08, Mark Sapiro wrote:
After some off list back and forth, Alan determined that the problem was that the mailman user had /bin/false as a login shell. Once that was changed, the script worked as expected.
Was this on a Solaris box? I've had problems with them lately not allowing cron jobs to run under a specific userid, even if they were in the /etc/cron.allow list, unless the user had a valid password hash and a valid shell.
One of the more screwed-up things I've seen from a Solaris box lately, I tell you....
-- Brad Knowles <[EMAIL PROTECTED]> LinkedIn Profile: <http://tinyurl.com/y8kpxu> ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
