Purify maintains suppressions in .purify files. You can share suppressions between programs by copying suppression directives into directories used by other programs, and by creating standard suppressions for your entire site.
Purify reads suppressions from all .purify files, processing them in the order listed below. If there are conflicting suppression directives, it is the directive Purify reads last that is applied. This is true of conflicting directives within files, and conflicting directives in different files.
To create suppressions for all Purify'd programs in a specific directory, use the .purify file in that directory. When you click Make permanent in the Suppressions dialog, this is where Purify saves the suppression directive by default.
To create suppressions for all Purify'd programs that you run, use the .purify file in your home directory, $HOME.
To create suppressions for all Purify'd programs at your site, use the default .purify file in the <purifyhome> directory. If this file is not writable, request that someone with permission add the directive.
By default, Purify suppresses UMC errors in the <purifyhome>/.purify file. You can unsuppress UMC errors in a location with higher precedence than this one.
To create suppressions for a specific operating system, use the.purify.solaris2, .purify.hpux, or .purify.irix files in the program directory, the $HOME directory, or the <purifyhome> directory. These files take precedence over other suppressions in the same directory.
You can use the -suppression-filenames option to instruct Purify to look for suppressions in specific files. This is helpful when you want to create different suppressions for two programs located in the same directory.