[EMAIL PROTECTED] wrote on 01/23/2008 04:27:49
PM:
> Hi,
> I am currently relying on the RPT timestamp in order to
> know when there is a change in the RPT data. I looked at the code
> and found that, for example, when the resource tag or the resource
> severity is changed, there is no timestamp update. I don?t see also
> any timestamp changes when there is a sensor threshold change.
>
> I would like to know the meaning of the timestamp and when it is
> used? For now, I see that the timestamp is added only when a
> resource (RPT) is added or removed.
>
If a plugin adds or removes an entry to/from the table then the counter
and timestamp are updated. If the entry already existed, then it ends up
being an overwrite/update.
They are not updated due to calling saHpiResourceSeveritySet() or
saHpiResourceTagSet(). This is consistent with how the other
counters/timestamps (DRT, DAT, DEL) work in that they are not affected by
the HPI user.
The intent for the counters is to let the user know that the
implementation has changed the tables, which is different from when
another HPI user changed something. Is the latter your case?
--Renier
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
