This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/16285] thread-safe file locking (using lock file)
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 03 Dec 2013 00:41:16 +0000
- Subject: [Bug libc/16285] thread-safe file locking (using lock file)
- Auto-submitted: auto-generated
- References: <bug-16285-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16285
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #1 from Rich Felker <bugdal at aerifal dot cx> ---
Could you clarify the intended usage case? I'm not clear on why this
functionality is essential, and perhaps knowing what you need it for would help
in recommending an alternate solution.
In any case, new open flags are a kernel matter; glibc has nothing to do with
getting such a feature added, but would need to add the macro to its headers if
it were added.
BTW, the bits of the open flags int are almost exhausted, so asking for new
features there is really not appropriate unless they're extremely important.
--
You are receiving this mail because:
You are on the CC list for the bug.