Re: How do I find the process triggering the SELinux alert?

Marius,

You can install lastcomm and see if lastcomm can keep the history of the
pid=3953.
Run after boots up:
lastcomm --debug|grep 3953

---henry

On Sat, Jun 17, 2023 at 10:39 AM Marius Ghita <[email protected]>
wrote:

> I have the following audit message
>
> Raw Audit Messages
> type=AVC msg=audit(1687022594.74:347): avc:  denied  { mmap_zero } for
>  pid=3953 comm="check" scontext=system_u:system_r:spc_t:s0
> tcontext=system_u:system_r:spc_t:s0 tclass=memprotect permissive=0
>
> This warning gets triggered from time to time around system startup, and I
> cannot find the process involved. The name check is too generic to use the
> locate command and the process is no longer running by the time I would
> have the chance to peek at the PID.
>
> Thanks.
> _______________________________________________
> selinux mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>

_______________________________________________
selinux mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue