selinux preventing clamd and amavisd even in Permissive

[John Griffiths]

I realize now that it was not selinux preventing the socket from being 
created. The combination of symptoms seemed to indicate that selinux was 
the culprit when in reality, it was clamav and freshclam.

Thanks for the reply.

Regards,
John

Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> John Griffiths wrote:
>   
>> I think I figured it out.
>>
>> I had not configured freshclam yet. Even though clamav had the default
>> virus databases from clamav-data.i386, clamav system would not start
>> until freshclam had updated the databases. I configured freshclam before
>> I went out. Apparently, when cron updated the virus databases, clamav
>> started normally and opened the missing socket and the email system
>> started working properly.
>>
>> At least this is my best deduction.
>>
>> I don't remember having to have freshclam configured for updates prior
>> to email working in Fedora 7. Guess this is a question for a different
>> list, but I just wanted to put things to rest.
>>
>> Regards,
>> John
>>
>> -- 
>> fedora-selinux-list mailing list
>> fedora-selinux-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-selinux-list
>>     
> In permissive mode, SELinux will not prevent anything from happening
> although it will report avc messages like it did.  setroubleshoot will
> still interpret these messages like SELinux had prevented the access.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFHVC01rlYvE4MpobMRAvrYAKC4lf8rCHTT5lsHMONHV2ZABoubVACgtl5z
> kZ62NmqbIuUdAIncJJNG/NY=
> =Vca9
> -----END PGP SIGNATURE-----
>