IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Agent configuration and environment variables > Persistent configuration changes > Linux or UNIX persistent configuration changes > Making persistent configuration changes
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Example 2: Altering an existing variable KDC_FAMILIES
The KDC_FAMILIES environment variable is particularly challenging because much of the data is created from the .ConfigData/kxxenv dialog file.
For example, suppose that in the existing .config file the KDC_FAMILIES variable looks similar to the following variable:
export KDC_FAMILIES='ip.pipe port:1918 ip use:n ip.spipe use:n sna use:n HTTP:1920'But you must have ephemeral:y added. In this case, the contents of the xx.environment file might be similar to the following variable:
KDC_FAMILIES=ip.pipe port:1918 ephemeral:y ip use:n ip.spipe use:n sna use:n HTTP:1920A more robust content line might be written as follows:
KDC_FAMILIES=ephemeral:y ${KDC_FAMILIES}
Create an xx.environment file for each product that you need to modify. That way your overrides persists for upgrades in current releases, and in future releases.
Parent topic:
Making persistent configuration changes