[Bug 766990] New: multifilesink: 'buffer'-mode writes no longer atomic

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=766990

            Bug ID: 766990
           Summary: multifilesink: 'buffer'-mode writes no longer atomic
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: ursula at kangatronix.co.uk
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

f1ceaab02f3f557e23b77b14771a575788f92bb4 changed the behaviour of the file
writing. Before the commit, g_file_set_contents was used for the 'buffer'
next-file mode of multifilesink.

Sample use case: I have a pipeline producing JPEG buffers. I want to store the
latest JPEG at a fixed location on the file system, which is exposed by a web
server. The latest frame can then be pulled down at a known HTTP URL from
another client on the network.

With the earlier code that used g_file_set_contents, things worked nicely, as
another process (e.g. the web server) reading the file would always have access
to a complete buffer, as g_file_set_contents writes to a temporary file, before
moving that over to the final destination (it also calls fsync, if necessary).
The new code, on the other hand, fwrites directly to the destination file,
truncating any existing data, so now there is a race.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.