Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== BASH - Files - Read a file - Troubleshooting - Prevent other commands from "eating" the input ======

Some commands greedily eat up all available data on standard input.

For example:

<code bash>
while read -r line; do
  cat > ignoredfile
  printf '%s\n' "$line"
done < "$file"
</code>

<WRAP info>
**NOTE:**  This will only print the contents of the first line.

The remaining content will go to "ignoredfile", as cat slurps up all available input.

</WRAP>

----

One workaround is to use a numeric FileDescriptor rather than standard input:

<code bash>
# Bash
while IFS= read -r -u 9 line; do
  cat > ignoredfile
  printf '%s\n' "$line"
done 9< "$file"
</code>

<WRAP info>
**NOTE:**  **read -u** is not portable to every shell.

Use a redirect to ensure it works in any POSIX compliant shell:

<code bash>
while IFS= read -r line <&9; do
  cat > ignoredfile
  printf '%s\n' "$line"
done 9< "$file"
</code>

or:

<code bash>
exec 9< "$file"
while IFS= read -r line <&9; do
  cat > ignoredfile
  printf '%s\n' "$line"
done
exec 9<&-
</code>

This example will wait for the user to type something into the file ignoredfile at each iteration instead of eating up the loop input.

Other commands that act this way include ssh and ffmpeg.

</WRAP>