Performing atomic write operations in a file in bash

After going through the bash documentation, this question and this one it’s still not clear to me how can I perform atomic write (append) operations to a file in bash. I have a script that is run in multiple instances and at some point must write data to a file:

echo "$RESULT" >> `pwd`/$TEMP_DIR/$OUT_FILE

How is it possible to make all write operations from all concurrently running scripts to that file atomic (so that data from one instance doesn’t overlap data from another)?

Contents hide

Answers:

Method 1

Method 2

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

It seems you need to use flock as in the example from man (http://linux.die.net/man/1/flock)

(
flock -x 200

# Put here your commands that must do some writes atomically

) 200>/var/lock/mylockfile

And put all your commands that must be atomic in ().

Method 2

flock is one of the ways of interlocking operations. The utility is part of the util-linux toolset and is only available for Linux. Other utilities, available across a wider range of platforms, are based around Daniel J. Bernstein’s setlock utility from his daemontools package:

setlock from daemontools
setlock from Bruce Guenter’s daemontools-encore
s6-setlock from Laurent Bercot’s s6
chpst from Gerrit Pape’s runit
runlock from Wayne Marshall’s perp
setlock from my nosh toolset

These tools operate with a slightly different paradigm to that used in M. Kurenkov’s answer (one that flock can also employ, but does not in that answer). One invokes the setlock program to chain load to the command that must be interlocked. setlock itself opens and locks the lock file, and leaves a file descriptor for it open in its process. The lock persists for as long as that process does (unless the subsequent command chained to explicitly releases the lock by finding and closing the open file descriptor).

For the case in the question one must interlock the command that produces the output line, being aware that this invokes an external echo in place of a shell built-in echo command:

setlock mylockfile echo "$RESULT" >> ./$TEMP_DIR/$OUT_FILE

In this case it is not necessary to interlock opening the output file in append mode. If it were, one would have to open that file within the lock, which necessitates either using programs like fdredir/redirfd:

setlock mylockfile fdredir --append 1 "./$TEMP_DIR/$OUT_FILE" echo "$RESULT"

which one can turn into a shell function if one wants:

outfile() { setlock mylockfile fdredir --append 1 "./$TEMP_DIR/$OUT_FILE" "[email protected]" ; }
[…]
outfile echo "$RESULT"

or sticking with the shell syntax and having it interpreted by a second shell running under the interlock, requiring some non-trivial quoting if one’s shell variables are not exported as environment variables:

setlock mylockfile sh -c 'echo '"$RESULT"' >> "./'$TEMP_DIR'/'$OUT_FILE'"'

This of course generalizes to things other than writing to output files:

setlock mylockfile sh -c '… interlocked ; stuff …'

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes

Article Rating