public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/10814] New: utmp locking uses alarm() which can't fully restore timer
@ 2009-10-20 10:08 did447 at gmail dot com
2009-10-20 11:30 ` [Bug libc/10814] " drepper at redhat dot com
0 siblings, 1 reply; 3+ messages in thread
From: did447 at gmail dot com @ 2009-10-20 10:08 UTC (permalink / raw)
To: glibc-bugs
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/10814] utmp locking uses alarm() which can't fully restore timer
2009-10-20 10:08 [Bug libc/10814] New: utmp locking uses alarm() which can't fully restore timer did447 at gmail dot com
@ 2009-10-20 11:30 ` drepper at redhat dot com
0 siblings, 0 replies; 3+ messages in thread
From: drepper at redhat dot com @ 2009-10-20 11:30 UTC (permalink / raw)
To: glibc-bugs
------- Additional Comments From drepper at redhat dot com 2009-10-20 11:30 -------
This is how it always worked and it does indeed work. Some programs might
depend or expect this horrible implementation. These interfaces are badly
designed due to the historic bagage and you have to know how and when to use them.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/10814] utmp locking uses alarm() which can't fully restore timer
[not found] <bug-10814-131@http.sourceware.org/bugzilla/>
@ 2014-07-01 5:39 ` fweimer at redhat dot com
0 siblings, 0 replies; 3+ messages in thread
From: fweimer at redhat dot com @ 2014-07-01 5:39 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=10814
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-07-01 5:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-20 10:08 [Bug libc/10814] New: utmp locking uses alarm() which can't fully restore timer did447 at gmail dot com
2009-10-20 11:30 ` [Bug libc/10814] " drepper at redhat dot com
[not found] <bug-10814-131@http.sourceware.org/bugzilla/>
2014-07-01 5:39 ` fweimer at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).