public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/16285] thread-safe file locking (using lock file) Date: Fri, 10 Jan 2014 23:33:00 -0000 [thread overview] Message-ID: <bug-16285-131-TFTlAq1zWF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16285-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16285 Ondrej Bilka <neleai at seznam dot cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |neleai at seznam dot cz Resolution|--- |INVALID --- Comment #7 from Ondrej Bilka <neleai at seznam dot cz> --- I agree with Rich here, link with checking EEXIST suffices. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-10 23:33 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-02 21:53 [Bug libc/16285] New: " wolfgang at contre dot com 2013-12-03 0:41 ` [Bug libc/16285] " bugdal at aerifal dot cx 2013-12-03 3:52 ` wolfgang at contre dot com 2013-12-03 4:04 ` bugdal at aerifal dot cx 2013-12-03 13:17 ` wolfgang at contre dot com 2013-12-03 13:26 ` wolfgang at contre dot com 2013-12-03 17:51 ` bugdal at aerifal dot cx 2013-12-22 18:27 ` carmelo73 at gmail dot com 2014-01-10 23:33 ` neleai at seznam dot cz [this message] 2014-01-11 6:08 ` wolfgang at contre dot com 2014-01-11 11:37 ` neleai at seznam dot cz 2014-06-13 11:50 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-16285-131-TFTlAq1zWF@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).