Software initialisation configuration files have open read/write permissions, and anyone can modify them. In some cases, you may want to restrict access to the files using the chmod command.

Here are some basic guidelines for modifying software initialisation configuration files:

• Do not modify the sample software initialisation configuration files. Make copies of the samples and work on those instead.
• Create a backup of a file before making any changes to it.
• After modifying a software initialisation configuration file, restart the software for the changes to take effect.
• To launch the software with a custom software initialisation configuration file, use the -c start-up option. For example:

  smoke -c /usr/discreet/smoke_2010/cfg/my_custom_init.cfg

  NoteIf you saved your custom software initialisation configuration file in a directory other than /usr/discreet/<product_home>/cfg, be sure to use the full directory path. If the custom file is not found, the application automatically uses the default init.cfg file.