The ProTop client has been enhanced to be more responsive to configuration changes, setting the stage for eliminating the need to alter existing configurations to accommodate new parameters.
This new configuration file follows the standard ProTop config file naming hierarchy from most general to most specific BUT, unlike old-style configurations, the files are additive. Rather than the most specific file “winning” and being used solely, the entries in the files along the way are accumulated. In the case of multiple entries for a property, the last entry wins. This means that customization is simpler – detailed configuration only needs to specify changes and additions. (The “api key” feature also uses this new-style configuration approach.)Changes to the config files, or the addition of previously missing detailed config files, will be noticed and the properties will be updated in near real time (there is a user configurable delay to prevent excessive resource consumption). Previously most shared variables were only settable at startup by way of the bin/localenv mechanism. Changes made post-startup would not be seen by a running pt3agent or by other ProTop client processes. This new configuration approach changes all that.