On Thu, 29 Dec 2005, Alexander Dalloz wrote:
If you face such issues where the unix permissions match but you get
permission denied, then have a look at the SELinux logging output
(either messages syslog file or when auditd runs in audit.log). You may
temporary set SELinux into permissive mode by following command:
setenfore=0. In that mode SELinux just documents what it thinks about
actions of the system and logs them, but does not deny these actions.
No, I have SELinux off there.
The problem was at a higher directory for which mailman did not have
execute (move into the directory) permission, so it couldn't stat the file
(or directory in this case) because it counldn't get there.
The strange thing is that mailman's check_perms said that everything was
OK, so I thing the logic of that script should get changed (sending a
mail to the mailman list so they know).
--
11:50:02 up 7 days, 23:02, 1 user, load average: 0.00, 0.02, 0.00
---------------------------------------------------------
Lic. Martín Marqués | SELECT 'mmarques' ||
Centro de Telemática | '@' || 'unl.edu.ar';
Universidad Nacional | DBA, Programador,
del Litoral | Administrador
---------------------------------------------------------------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
