Bug 189595 - ftime rollover off by one
Summary: ftime rollover off by one
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: time
Version: 3.0
Hardware: v850
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-21 14:23 UTC by stefano
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-04 12:35:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description stefano 2006-04-21 14:23:12 UTC
ftime rollover off reading an application log .
In particular an event temporary younger had a timestamp (obtained calling 
ftime) older than 1 milliseconds

Comment 1 Florian La Roche 2006-04-23 17:03:13 UTC
Should this get reported against the kernel?

Thanks,

Florian La Roche


Comment 2 stefano 2006-05-02 05:38:15 UTC
(In reply to comment #1)
> Should this get reported against the kernel?
> Thanks,
> Florian La Roche

I didn't understand the question ?
Thanks

Stefano

Comment 3 Florian La Roche 2006-05-10 13:46:10 UTC
Hello Stefano,

can you add more information on what this bug should be
and what change you would like to see?

Are you talking about the glibc implementation of ftime(3)?
("man 3 ftime")

regards,

Florian La Roche


Comment 4 stefano 2006-05-16 07:52:30 UTC
(In reply to comment #3)
> Hello Stefano,
> can you add more information on what this bug should be
> and what change you would like to see?
> Are you talking about the glibc implementation of ftime(3)?
> ("man 3 ftime")
> regards,
> Florian La Roche

Yes we are using the ftime function
Thanks 

Stefano

Comment 5 Florian La Roche 2006-11-04 12:35:55 UTC
This component is about a user space app. Please open a new report about
glibc or kernel problems with a detailed reproducer if this is still a
problem.

regards,

Florian La Roche



Note You need to log in before you can comment on or make changes to this bug.