В #selinx рассказывают: <ckorzhik> /var/lib/zabbix - is home of zabbix, and here placed my scripts <tfirg_> why? <tfirg_> why there? <ckorzhik> because is home of zabbix ._. <ckorzhik> where i must to put them? <tfirg_> cant you not just put them /usr/local/bin or something? <ckorzhik> sounds reasonable <ckorzhik> now try to replace in /usr/local/bin <tfirg_> they should end up with bin_t type i suspect <tfirg_> which would be good ... <tfirg_> run sepolgen_ifgen if it is installed <tfirg_> sepolgen_ifgen <tfirg_> then try again <tfirg_> if its not installed then forget it <tfirg_> its not worth the trouble to install it ... <ckorzhik> usr/share/selinux/devel/Makefile <ckorzhik> is it important? May be build as in man? <tfirg_> yes you can also try building as in man <tfirg_> although not sure which man you are referring to <tfirg_> man checkmodule <tfirg_> man semodule_package <tfirg_> actually that probably wont work... <tfirg_> yum install selinux-policy-devel <tfirg_> you can yum erase it when you are done ... <tfirg_> matchpathcon /var/lib/zabbix <tfirg_> seinfo -t| grep zabbix ... <ckorzhik> why this syntax is not same as in audit2allow output? <tfirg_> sesearch -ASCT -s zabbix_agent_t -t tmp_t | grep type_transition <ckorzhik> ^ empty <tfirg_> its a abstracted version of the language for easy maintenance ... <ckorzhik> where i can read about abstracted version of language? <tfirg_> well its just m4 macros <tfirg_> so if you learn abit about m4 macro language and then look in the headers then it should make a little bit of sense <tfirg_> the headers are here: <tfirg_> /usr/share/selinux/devel/include/