[Bug libc/10814] New: utmp locking uses alarm() which can't fully restore timer

did447 at gmail dot com sourceware-bugzilla@sourceware.org
Tue Oct 20 10:08:00 GMT 2009


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.



More information about the Glibc-bugs mailing list