Differences between revisions 4 and 8 (spanning 4 versions)
Revision 4 as of 2008-11-22 14:09:51
Size: 1392
Editor: localhost
Comment: converted to 1.6 markup
Revision 8 as of 2010-07-01 19:01:15
Size: 1777
Editor: WillDye
Comment: Non-working examples should be flagged as such within the code
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Typically you'll see this behaviour in situations like these:
Line 4: Line 5:
Typically you'll see this behaviour in situations like these:
Line 6: Line 6:
  # Non-working example
Line 11: Line 12:
Line 12: Line 14:
  # Non-working example
Line 27: Line 30:
Notice the redirection on the ffmpeg line: `</dev/null`. See the [[BashGuide/TheBasics/InputAndOutput#Redirection|redirection section]] of the BashGuide for more information on this. Notice the redirection on the ffmpeg line: `</dev/null`. See the [[BashGuide/InputAndOutput#Redirection|redirection section]] of the BashGuide for more information on this.
Line 30: Line 33:

Sometimes with large loops it might be difficult to work out what's reading from stdin; or a program might change its behaviour when you add `</dev/null` to it. In this case you can make read use a different file descriptor that a random program is less likely to read from:
{{{
  while read <&3 line; do
    ......
  done 3<file
}}}

I'm using a loop which runs once per line of input but it only seems to run once; everything after the first line is ignored?

Typically you'll see this behaviour in situations like these:

  # Non-working example
  while IFS= read -r file; do
    ffmpeg -i "$file" -vcodec libxvid -acodec libfaac -ar 32000 \
      "${file%.avi}".mkv
  done < <(find . -name '*.avi')

  # Non-working example
  while read host; do
    ssh "$host" command
  done <hostslist

What's happening here? Let's take the first example. read reads a line from standard input (FD 0), puts it in the file parameter, and then ffmpeg is executed. Like any program you execute from BASH, ffmpeg inherits standard input, which for some reason it reads. I don't know why. But in any case, when ffmpeg reads stdin, it sucks up all the input from the find command, starving the loop.

Here's how you make it work:

  while IFS= read -r file; do
    ffmpeg </dev/null -i "$file" -vcodec libxvid -acodec libfaac -ar 32000 \
      "${file%.avi}".mkv
  done < <(find . -name '*.avi')

Notice the redirection on the ffmpeg line: </dev/null. See the redirection section of the BashGuide for more information on this.

The ssh example can be fixed the same way, or with the -n switch (at least with OpenSSH).

Sometimes with large loops it might be difficult to work out what's reading from stdin; or a program might change its behaviour when you add </dev/null to it. In this case you can make read use a different file descriptor that a random program is less likely to read from:

  while read <&3 line; do
    ......
  done 3<file

BashFAQ/089 (last edited 2024-04-13 21:56:35 by Reg)