Setroubleshoot question

[Daniel J Walsh]

Jay Cliburn wrote:
> Is it a bug that setroubleshoot_dispatcher continues to run even when 
> setroubleshoot is shut off?
>
setroubleshoot_dispatcher is going away.  It is being combined into 
setroubleshoot. So yes this is a bug.
> [[root at osprey ~]# rpm -q setroubleshoot
> setroubleshoot-0.16-1
>
> root at osprey ~]# service setroubleshoot status
> setroubleshoot is stopped
>
> [root at osprey ~]# ps -ef | grep setrou
> root      1783  1770  0 20:55 ?        00:00:00 python 
> /usr/lib/audit/setroubleshoot_dispatcher
> root      2558  2523  0 21:29 pts/0    00:00:00 grep setrou
>
> [root at osprey ~]# tail -100 /var/log/messages | grep setrouble
> Aug  4 20:56:12 osprey setroubleshoot: 2006-08-04 20:56:12,711 
> [ipc.ERROR] exiting after [Errno 2] No such file or directory, socket 
> AlertClient: socket=/var/run/setroubleshoot/setroubleshoot_server 
> user=None
>
> Thanks,
> Jay
>
> -- 
> fedora-selinux-list mailing list
> fedora-selinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-selinux-list