|
Size: 1777
Comment: Non-working examples should be flagged as such within the code
|
Size: 1852
Comment: reword question a bit
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| == 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: |
== I'm reading a file line by line and running ssh or ffmpeg, only the first line gets processed! == When [[BashFAQ/001|reading a file line by line]], if a command inside the loop also reads stdin, it can exhaust the input file. For example: |
| Line 8: | Line 8: |
| ffmpeg -i "$file" -vcodec libxvid -acodec libfaac -ar 32000 \ "${file%.avi}".mkv |
ffmpeg -i "$file" -vcodec libxvid -acodec libfaac -ar 32000 "${file%.avi}".mkv |
| Line 16: | Line 15: |
| ssh "$host" command | ssh "$host" some command |
| Line 25: | Line 24: |
| ffmpeg </dev/null -i "$file" -vcodec libxvid -acodec libfaac -ar 32000 \ "${file%.avi}".mkv |
ffmpeg -i "$file" -vcodec libxvid -acodec libfaac -ar 32000 "${file%.avi}".mkv </dev/null |
| Line 30: | Line 28: |
| Notice the redirection on the ffmpeg line: `</dev/null`. See the [[BashGuide/InputAndOutput#Redirection|redirection section]] of the BashGuide for more information on this. | Notice the [[BashGuide/InputAndOutput#Redirection|redirection]] on the ffmpeg line: `</dev/null`. The ssh example can be fixed the same way, or with the `-n` switch (at least with [[http://www.openssh.org/|OpenSSH]]). |
| Line 32: | Line 30: |
| The ssh example can be fixed the same way, or with the `-n` switch (at least with [[http://www.openssh.org/|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: |
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 FileDescriptor that a random program is less likely to read from: |
| Line 40: | Line 36: |
or use read's `-u` option (Not POSIX): {{{ # Bash while read -u 3 line; do ...... done 3<file }}} |
I'm reading a file line by line and running ssh or ffmpeg, only the first line gets processed!
When reading a file line by line, if a command inside the loop also reads stdin, it can exhaust the input file. For example:
# 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" some command
done <hostslistWhat'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 -i "$file" -vcodec libxvid -acodec libfaac -ar 32000 "${file%.avi}".mkv </dev/null
done < <(find . -name '*.avi')Notice the redirection on the ffmpeg line: </dev/null. 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 FileDescriptor that a random program is less likely to read from:
while read <&3 line; do
......
done 3<fileor use read's -u option (Not POSIX):
# Bash
while read -u 3 line; do
......
done 3<file