What would be the best approach to attack this: One application, multiple components/daemons. Some files are specific to a daemon, some are shared between them (eg. log files are unique, some config files, keystores... are shared etc.) All daemons start from a single init script and I am not allowed to change it. Options: 1. Create policy for each component and then domain transition between them (what about shared files???) 2. Create a single policy for multiple daemons? Any advice... -- Mladen Sekara <dev@xxxxxxxxxx> _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
