From wwwrun@oss.sgi.com Wed Jan 1 14:00:22 2014
Return-Path:
Bug ID
1042
Summary
rpm pmda doesn't support multiple-version rpms
Product
pcp
Version
unspecified
Hardware
All
OS
Linux
Status
NEW
Severity
major
Priority
P5
Component
pcp
Assignee
scox@redhat.com
Reporter
fche@redhat.com
CC
pcp@oss.sgi.com
Classification
Unclassified
On my f19 machine:
% rpm -q kernel-devel
kernel-devel-3.11.10-200.fc19.x86_64
kernel-devel-3.12.5-200.fc19.x86_64
% pminfo -f rpm.version| grep kernel-devel
inst [2514 or "kernel-devel"] value "3.11.10"
(note the 3.12.5 info is missing)
Similarly for other RPMs of whom more than one version/release is concurrently
installed. (Having multiple versions like this is normal.)
The rpm pmda should not use rpm "n" (name) as its key instance-domain,
but rather the whole n-v-r-a string, or (if possible) some rpmlib
internal unique & persistent identifier. (It is possible, though not
quite normal, for the exact same n-v-r-a rpm to be installed multiple
times.)
| What | Removed | Added |
|---|---|---|
| CC | nathans@debian.org |
One other thing worth mentioning - there are also configure options (--with-user and --with-group) for overriding pcp user/group if needed. It is preferable to use the default values here whenever possible though.
| What | Removed | Added |
|---|---|---|
| CC | nathans@debian.org |
Some potentially useful discussion here, Stan: https://lists.dulug.duke.edu/pipermail/rpm-devel/2006-October/001702.html We'll need to (re)introduce the rpm.name metric I foolishly claimed was no longer needed too. :) cheers.