On Wed, 2009-05-13 at 07:20 +0200, Fabio M. Di Nitto wrote: > On Tue, 2009-05-12 at 21:43 -0700, Steven Dake wrote: > > On Tue, 2009-05-12 at 20:37 +0200, Fabio M. Di Nitto wrote: > > > On Tue, 2009-05-12 at 18:11 +0200, Jan Friesse wrote: > > > > This is first part of uid-gid function. Add support for reading > > > > directory (now it's SYSCONFIG/ais/security, > > > > > > might be a good idea to discuss config dirs and files one minute here.. > > > > > > corosync uses /etc/corosync.conf > > > openais (via corosync) /etc/ais/openais.conf (that's basically a > > > duplicate of corosync.conf) > > > amf service reads /etc/ais/amf.conf > > > > > > _maybe_ we should make them consistent before we add new entries like > > > ais/security... > > > > > > Fabio > > > > I think how we should proceed is as follows: > > /etc/corosync/corosync.conf > > /etc/corosync/authkey contains security authkey > > /etc/corosync/corosync/uidgid contains list of authorized ipc users for > > corosync > > /etc/corosync/openais/amf.conf contains amf config file > > /etc/corosync/openais/openais.conf - specific openais config options > > /etc/corosync/openais/uidgid - contains list of security IPC connections > > for openais > > /etc/corosync/serviceXXX/XXX contains uidgid for other services as well > > as service specific config files > > > > The current /etc/openais.conf can then be merged into corosync.conf. > > > > After some more thinking, security uidgid could be done this way: > > /etc/corosync/uidgid.d/service_name > > at this point the reference directory is set (.d is very common for > config directories) and we read all the config bits from there. > > Fabio
Honzaf, We are in agreement then. Honzaf, can you implement this spec? regards -steve _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
