SCIENTIFIC-LINUX-USERS Archives

July 2017

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Andrew C Aitchison <[log in to unmask]>
Reply To:
Andrew C Aitchison <[log in to unmask]>
Date:
Tue, 18 Jul 2017 17:03:40 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
On Tue, 18 Jul 2017, Stephen Isard wrote:

> On Mon, 17 Jul 2017 23:52:22 +0200, Maarten <[log in to unmask]> wrote:
>
>> The process exim running with the the selinux context exim_t is trying
>> to access the directory /proc/net which has the selinux context
>> sysctl_net_t.
>>
>> Causing selinux to block access to directory, because the source context
>> is different from the destination context.
>
> Yes, thank you, I've got that part.  As I said earlier, what I am wondering now is why exim is trying to search that directory, and whether I want it to.
> It happens at - to me - unpredictable times, apparently unrelated to any messages being sent or received.

Looking at the upstream source for exim 4.89, there are two lots of 
references to /proc
1) /proc/loadavg 
2) /proc/net/if_inet6
unsuprisingly exim uses these to determine load average and
IPv6 address etc...

I don't know whether the binary rpms add any other uses of /proc
- which version of exim are you using - the one from epel ?

-- 
Andrew C Aitchison					Cambridge, UK

ATOM RSS1 RSS2