Menu

#1617 imm: change time(NULL) to osaf_clock_gettime(CLOCK_MONOTONIC, ...)

5.0.FC
fixed
None
enhancement
imm
nd
major
2016-03-18
2015-12-03
No

When the system time is changed, IMM can time out search results, CCBs...
IMM should not depend on the system time.

Wherever in IMM we have time(NULL) for calculating timeouts, we should change it to osaf_clock_gettime(CLOCK_MONOTONIC, ...).
Changing system time does not change monotonic time.

Related

Tickets: #1617
Tickets: #1704
Wiki: ChangeLog-5.0.0

Discussion

  • Anders Widell

    Anders Widell - 2015-12-03
    • summary: imm: change time(NULL) to clock_gettime(CLOCK_MONOTONIC, ...) --> imm: change time(NULL) to osaf_clock_gettime(CLOCK_MONOTONIC, ...)
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,5 +1,5 @@
     When the system time is changed, IMM can time out search results, CCBs...
     IMM should not depend on the system time.
    
    -Wherever in IMM we have time(NULL) for calculating timeouts, we should change it to clock_gettime(CLOCK_MONOTONIC, ...).
    +Wherever in IMM we have time(NULL) for calculating timeouts, we should change it to osaf_clock_gettime(CLOCK_MONOTONIC, ...).
     Changing system time does not change monotonic time.
    
     
  • Neelakanta Reddy

    • status: unassigned --> assigned
    • assigned_to: Neelakanta Reddy
    • Milestone: future --> 5.0.FC
     
  • Neelakanta Reddy

    • status: assigned --> accepted
     
  • Neelakanta Reddy

    • status: accepted --> review
     
  • Neelakanta Reddy

    • status: review --> fixed
    • Part: - --> nd
     
  • Neelakanta Reddy

    changeset: 7334:8bf0ce8c5f87
    tag: tip
    user: Neelakanta Reddy
    date: Fri Mar 18 11:52:18 2016 +0530
    summary: imm: changing from system time to monotonic time [#1617]

     

    Related

    Tickets: #1617


Log in to post a comment.

MongoDB Logo MongoDB