At boot time I have initlog being run from a dhclient, and initlog then runs minilogd.
Currently the strict SE Linux policy does not permit minilogd to be run. What is needed is the following rule:
domain_auto_trans(dhcpc_t, syslogd_exec_t, syslogd_t)
However there may be other instances of this problem. It seems that dhclient is run from hotplug or something which makes it start before the main syslogd starts. Do we have any idea of what else might potentially be started in such a manner?
Russell Coker (russell@coker.com.au) said:
At boot time I have initlog being run from a dhclient, and initlog then runs minilogd.
Currently the strict SE Linux policy does not permit minilogd to be run. What is needed is the following rule:
domain_auto_trans(dhcpc_t, syslogd_exec_t, syslogd_t)
However there may be other instances of this problem. It seems that dhclient is run from hotplug or something which makes it start before the main syslogd starts. Do we have any idea of what else might potentially be started in such a manner?
network starts before syslog, so it's more or less expected.
Bill