http://defect.opensolaris.org/bz/show_bug.cgi?id=11784
--- Comment #14 from Michael Hunter <michael.hunter at sun.com> 2009-10-08 14:06:53 UTC --- To further document why this function is a little weird I'm including an example I send to the ML. On Wed, October 7th, at 10:15.2 of a second I called this function with when = 1. I end up with an event on the queue for Wed, October 7th, at 10:16 (10:15.2 + 1 is 10:16). Timer set for 1 second from 10:15.2 at 10:16.2. On Wed, October 7th, at 10:16.1 I call with when = 1. I ended up with a queue that looks like 10:16, 10.17. I don't reset the timer because e->event_time - now is 0. If I don't do an expire in this timeframe and cancel the timer in that code then I let the timer run out to 10:16.2 coming close to the originally expected 1s. I then reset the timer to 10:17.2. On Wed October 7th at 10:16.9 I call with when = 1. Now the queue looks like 10:17, 10.18 and I reset the timer to 10:17.9 (note that the event which I originally scheduled for 10:17.2 ends up firing .7s later then that). -- Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
