On 2012-09-27T16:36:08, Ulrich Windl <[email protected]> wrote:
Hi Ulrich,
we always appreciate your friendly, constructive and non-condescending
feedback.
> However if you specify a duration like "P2", the duration is not added to the
> current time; instead the current time is used as lifetime (it seems):
"P2" does not specify a unit for the duration. So I'm not perfectly sure
what expected behavior would be.
> Sep 26 13:55:03 o1 cib: [13067]: info: cib:diff: + <date_expression
> id="cli-prefer-lifetime-end-prm_xen_s01" operation="lt" end="2013-07-26
> 11:55:03Z" />
If it's already Jul 26 2013 for you on Sep 26 2012, I'm amazed. ;-)
Admittedly, how "P2" ends up being expanded to 13 months I'm not sure.
> So when the change being logged includes up to the second exactly the current
> time, the duration is effectively ignored.
>
> Must IT be so complicated? If you insist on ISO syntax on one hand, I expect
> you understand the syntax correctly, so a duration has to be added to the
> current time to make any sense.
In your opinion, what time unit should it default to?
What happens when you specify "P2D", for example?
> To make things worse, why is crm shell displaying the time in UTC (in
> non-XML mode)? In Perl ist a simple "scalar localtime $time" that will
> make things easier to read.
We probably should make this optional, yes. Internally we need to store
it in UTC format.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
