File Name
Any name |
Description
This file is used to define RPM packages subject to Linux patch management.
Output file for the swcfmg_patch_exportrpmpolicy command (the Linux patch management target definition export command)
Input file for the swcfmg_patch_importrpmpolicy command (the Linux patch management target definition import command)
This file is specified as an option for the swcfmg_patch_importrpmpolicy command (the Linux patch management target definition import command), thereby registering definitions.
File Location
Any folder |
File Format
CSV format
[#]<rpm-name>,<rpm-architecture>,<rpm-version>,<rpm-release> ... |
Parameters
The following line is regarded as a single definition.
If an item includes a comma (",") or double quote ("), enclose the item in double quotes (").
Example:
"z,lib",x86_64,1.2.3,3
These parameters will be defined as below:
z,lib,x86_64,1.2.3,3
Also, if an item includes double quotes ("), enter two consecutive double quotes. Entering two consecutive double quotes expresses one double quote symbol.
Example:
"z""lib""",x86_64,1.2.3,3
These parameters will be defined as below:
z"lib",x86_64,1.2.3,3
In all other cases, there is no need to enclose items in double quotes ("). Double quotes are not needed for empty items either. Even if double quotes are used to enclose an item that does not require double quotes, the definition will still be valid.
Column | Item | Meaning | Value | Remarks |
|---|---|---|---|---|
- | # | Comment line | - | - |
1 | rpm-name | RPM package name | Example: yum | Cannot be omitted. |
2 | rpm-architecture | RPM package architecture | Example: noarch | - |
3 | rpm-version | RPM package version | Example: 3.2.22 | - |
4 | rpm-release | RPM package release | Example: 33.el5 | This item is valid if RPM package version (rpm-version) has been set. |
Cautions
Changes to the definition are reflected with the next discovery.
If multiple definitions have been set for the same RPM package name, the definition with the highest priority will take effect, in accordance with the following order of priorities. (Combinations with the widest scope have the highest priority.)
Priority | Column combination |
|---|---|
High ¯ Low | "rpm-name" |
"rpm-name", "rpm-architecture" | |
"rpm-name", "rpm-version" | |
"rpm-name", "rpm-architecture", "rpm-version" | |
"rpm-name", "rpm-version", "rpm-release" | |
"rpm-name", "rpm-architecture", "rpm-version", "rpm-release" |
If two combinations with the same priority are defined, both combinations will take effect.
Example:
zlib,i386,, zlib,x86_64,,
In the example above, both definitions take effect.
These settings do not perform authorization operations for RPM packages. These settings only set up RPM packages that are managed as Linux patches. Authorization operations are automatically performed when the infrastructure administrator registers RPM packages with the yum repository server.
Example
Defining only the RPM package name
zlib,,,
In this example, RPM packages such as zlib.x86_64 1.2.3-3, zlib.i386 1.2.3-3, zlib.x86_64 1.2.3-25.el6, zlib.i686 1.2.3-25.el6, zlib.x86_641.2.4-2 and zlib.i386 1.2.4-2 will be subject to patch management.
Defining the RPM package name and architecture
zlib,x86_64,,
In this example, RPM packages such as zlib.x86_64 1.2.3-3, zlib.x86_64 1.2.3-25.el6 and zlib.x86_64 1.2.4-2 will be subject to patch management.
Defining the RPM package name and version
zlib,,1.2.3,
In this example, RPM packages such as zlib.x86_64 1.2.3-3, zlib.i386 1.2.3-3, zlib.x86_64 1.2.3-25.el6 and zlib.i686 1.2.3-25.el6 will be subject to patch management.
Defining the RPM package name, architecture, and version
zlib,x86_64,1.2.3,
In this example, RPM packages such as zlib.x86_64 1.2.3-3 and zlib.x86_64 1.2.3-25.el6 will be subject to patch management.
Defining the RPM package name, version, and release
zlib,,1.2.3,3
In this example, RPM packages such as zlib.x86_64 1.2.3-3 and zlib.i386 1.2.3-3 will be subject to patch management.
Defining the RPM package name, architecture, version, and release (all items specified)
zlib,x86_64,1.2.3,3
In this example, only "zlib.x86_64 1.2.3-3" will be subject to patch management.
Mixing two definitions on the same RPM package name, one with just the RPM package name, and the other with the RPM package name and architecture
zlib,,, zlib,x86_64,,
The definition with just the RPM package name will take effect. (In this example, RPM packages such as zlib.x86_641.2.3-3, zlib.i386 1.2.3-3, zlib.x86_64 1.2.3-25.el6, zlib.i686 1.2.3-25.el6, zlib.x86_641.2.4-2 and zlib.i386 1.2.4-2 will be subject to patch management.)
