This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author matrixise
Recipients Sworddragon, docs@python, matrixise, r.david.murray
Date 2016-08-06.11:04:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470481465.94.0.822310462332.issue23105@psf.upfronthosting.co.za>
In-reply-to
Content
If you read the documentation from glibc-2.24, these options are only available on BSD and not on Linux.

"""
The remaining operating modes are BSD extensions. They exist only on some systems. On other systems, these macros are not defined.

Macro: int O_SHLOCK
Acquire a shared lock on the file, as with flock. See File Locks.

If O_CREAT is specified, the locking is done atomically when creating the file. You are guaranteed that no other process will get the lock on the new file first.

Macro: int O_EXLOCK
Acquire an exclusive lock on the file, as with flock. See File Locks. This is atomic like O_SHLOCK.
"""

With my fedora 24, and glibc 2.23 I don't find any reference to these macros.
History
Date User Action Args
2016-08-06 11:04:25matrixisesetrecipients: + matrixise, r.david.murray, docs@python, Sworddragon
2016-08-06 11:04:25matrixisesetmessageid: <1470481465.94.0.822310462332.issue23105@psf.upfronthosting.co.za>
2016-08-06 11:04:25matrixiselinkissue23105 messages
2016-08-06 11:04:25matrixisecreate