Tom London wrote:
OK, that cleared up the above issues.
One last thing: 'service setroubleshoot status' says:
setroubleshoot dead but subsys locked
[root@localhost contexts]# ps agx | grep setr
11350 ? Ssl 0:00 python /usr/sbin/setroubleshootd
11394 pts/0 S+ 0:00 grep setr
[root@localhost contexts]#
That right?
Should /etc/init.d/setroubleshoot check setroubleshootd (not
setroubleshoot)?
I changed as below to get 'service setroubleshoot status' to work.
Not sure if it is right.....
tom
--- setroubleshoot 2006-08-07 15:15:34.000000000 -0700
+++ foo 2006-08-08 12:31:59.000000000 -0700
@@ -88,7 +88,7 @@
stop
;;
status)
- status $prog
+ status $exe
;;
restart)
restart
Yes that is correct.
There is a new setroubleshoot out on people also, if you want to try it.
--
fedora-selinux-list mailing list
fedora-selinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-selinux-list
