[FFmpeg-devel] [PATCH 3/9] lavf/file: implement EXCL flag.
Reimar.Doeffinger at gmx.de
Sat Apr 19 13:38:04 CEST 2014
On Sat, Apr 19, 2014 at 10:49:02AM +0200, Nicolas George wrote:
> Le decadi 30 germinal, an CCXXII, Reimar Döffinger a écrit :
> > If yes, isn't it confusing to default to non-exclusive even though the
> > whole OS defaults to exclusive?
> I am not sure what you mean here, especially "exclusive" and
> "non-exclusive". As far as I know, currently, lavf will silently overwrite
> files on any platform, and this patch series does not change the default.
I didn't properly understand what it does.
The name EXCL tricked my mind into thinking it would also be about exclusive
access/locking (I had been thinking about that for other reasons).
To me that raises the question: Do we really want to take over the
horrible O_EXCL naming or should we rather call it something more
Also, will this feature ever work reliably actually?
It might create a false sense of security, which actually not working
without any possibility to even detect the cases where it does not work
(at least that's my impression reading the man page, and that's only for
More information about the ffmpeg-devel