He might want to run a strace -o appname.out -f
<startupappgettingtheerrorandoptions>
And then do the ausearch and we should be able to see what what the
pid was doing and/or what executable it was.
On Wed, Apr 14, 2021 at 1:52 PM Ed Greshko <ed.greshko(a)greshko.com> wrote:
>
> On 15/04/2021 00:33, home user wrote:
> > I tried that using "ps -ef | grep [pid]". The only hit was the ps
command itself.
>
> It is not clear to me that you did this immediately after getting the alert.
>
> According to the ausearch_out the PID is different at each instance of an alert. So,
it is possible that
> whatever process produced the alert has exited or died after the series of alerts.
>
> --
> Remind me to ignore comments which aren't germane to the thread.
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure