SC2094

grep foo file.txt | sed -e 's/foo/bar/g' > file.txt

grep foo file.txt  | sed -e 's/foo/bar/g' > tmpfile && mv tmpfile file.txt

Each step in a pipeline runs in parallel.

In this case, grep foo file.txt will immediately try to read file.txt while sed .. > file.txt will immediately try to truncate it.

This is a race condition, and results in the file being partially or (far more likely) entirely truncated.

Note that this can also be a problem when you write to a file and read from it later in the pipe. The second command (which reads the file) may not see all the output of the first. An exception in this case is a non-greedy file reader like less, for example python foo.py 2> errfile.txt | less - errfile.txt will successfully allow you to see stdout and stderr separately in less.

You can ignore this error if:

• The file is a device or named pipe. These files don't truncate in the same way.
• The command mentions the filename but doesn't read/write it, such as echo log.txt > log.txt.

• StackOverflow: bash redirect input from file back into same file
• BashPitfalls: cat file | sed s/foo/bar/ > file