.oafinfo search path.

To know the list of available CORBA servers on your local machine, the OAF daemon searches a number of directories for .oafinfo XML files which contain the description of the services offered by these servers. By default, OAF will try to find them in ${prefix}/share/oaf which may be a problem if users install other applications using OAF in different prefixes.

To work around this problem, OAF will parse a number of other directories. It will parse the directories listed in the OAF_INFO_PATH env variable. It will parse the prefixes listed in the GNOME_PATH env variable. If, for example, OAF_INFO_PATH=/opt/gnome/share/oaf:/opt/gnome/oaf/share/oaf, OAF will parse /opt/gnome/share/oaf and /opt/gnome/oaf/share/oaf If GNOME_PATH=/opt/gnome:/opt/gnome/oaf, OAF will parse /opt/gnome/share/oaf and /opt/gnome/oaf/share/oaf.

The above env variables are kept for compatibility purposes with older versions of OAF and for GNOME integration. OAF has a much nicer configuration file which allows you to control which directories are parsed by OAF. This XML configuration file is located in ${prefix}/etc/oaf/oaf-config.xml. An empty oaf-config.xml and a sample oaf-config.xml.sample file should be installed on your system.

It is recommended to use the oaf-sysconf command-line configuration tool to edit this file. However, here is an example of its format.

<?xml version="1.0"?>

<oafconfig>

<searchpath>
<item>/opt/gnome/share/oaf</item>
<item>/usr/local/gnome/share/oaf</item>
<item>/usr/local/share/oaf</item>
<item>/opt/gnome/oaf/share/oaf</item>
</searchpath>

<searchpath>
<item>/opt/gnome/oaf/share/oaf</item>
</searchpath>

</oafconfig>

There can be any number of <item> tags in a <searchpath> tag and any number of <searchpath tags in the <oafconfig> tag.