This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/10814] New: utmp locking uses alarm() which can't fully restore timer
- From: "did447 at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 20 Oct 2009 10:08:14 -0000
- Subject: [Bug libc/10814] New: utmp locking uses alarm() which can't fully restore timer
- Reply-to: sourceware-bugzilla at sourceware dot org
Hi,
A timer set with a non null it_interval via setitimer() is corrupted after a
call to utmp functions.
Maybe LOCK_FILE could use setitimer() rather than alarm() ?
--
Summary: utmp locking uses alarm() which can't fully restore
timer
Product: glibc
Version: 2.9
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: did447 at gmail dot com
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10814
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.