The Ice.Config property has special meaning to the Ice run time: it determines the pathname of a configuration file from which to read property settings. For example:
The ‑‑Ice.Config command-line option overrides any setting of the
ICE_CONFIG environment variable, that is, if the
ICE_CONFIG environment variable is set and you also use the
‑‑Ice.Config command-line option, the configuration file specified by the
ICE_CONFIG environment variable is ignored.
If you use the ‑‑Ice.Config command-line option together with settings for other properties, the settings on the command line override the settings in the configuration file. For example:
This sets the value of the Ice.MessageSizeMax property to
4096 regardless of any setting of this property in
/usr/local/filesystem/config. The placement of the
‑‑Ice.Config option on the command line has no influence on this precedence. For example, the following command is equivalent to the preceding one:
Settings of the Ice.Config property inside a configuration file are ignored, that is, you can set
Ice.Config only on the command line.
If you use the ‑‑Ice.Config option more than once, only the last setting of the option is used and the preceding ones are ignored. For example:
This causes property settings to be retrieved from /usr/local/filesystem/config, followed by any settings in the file
config in the current directory; settings in
./config override settings
/usr/local/filesystem/config. For C++, Python, Ruby, and .NET, this mechanism also works for configuration files specified via the
ICE_CONFIG environment variable.