I'm trying to read a text file and do something with each line, using a bash script.So, I have a list that looks like this:server1server2server3server4I thought I could loop over this using a while loop, like so:while read server; do  ssh $server uname -adone < /home/kenny/list_of_servers.txtThe while loop stops after 1 run, thus only running uname -a on server1However, with a for loop using cat it works fine:for server in $(cat /home/kenny/list_of_servers.txt) ; do  ssh $server uname -adoneEven more baffling to me is that this also works:while read server; do  echo $serverdone < /home/kenny/list_of_servers.txtWhy does my first example stop after the first iteration?
Reading lines from a file with bash: for vs. while
bash;files;io redirection
The for loop is fine here. But note that this is because the file contains machine names, which do not contain any whitespace characters or globbing characters. for x in $(cat file); do  does not work to iterate over the lines of file in general, because the shell first splits the output from the command cat file anywhere there is whitespace, and then treats each word as a glob pattern so \[?* are further expanded. You can make for x in $(cat file) safe if you work on it:set -fIFS=''for x in $(cat file); do Related reading: Looping through files with spaces in the names?; How can I read line by line from a variable in bash?; Why is while IFS= read used so often, instead of IFS=; while read..? Note that when using while read, the safe syntax to read lines is while IFS= read -r line; do .Now let's turn to what goes wrong with your while read attempt. The redirection from the server list file applies to the whole loop. So when ssh runs, its standard input comes from that file. The ssh client can't know when the remote application might want to read from its standard input. So as soon as the ssh client notices some input, it sends that input to the remote side. The ssh server there is then ready to feed that input to the remote command, should it want it. In your case, the remote command never reads any input, so the data ends up discarded, but the client side doesn't know anything about that. Your attempt with echo worked because echo never reads any input, it leaves its standard input alone.There are a few ways you can avoid this. You can tell ssh not to read from standard input, with the -n option.while read server; do  ssh -n $server uname -adone < /home/kenny/list_of_servers.txtThe -n option in fact tells ssh to redirect its input from /dev/null. You can do that at the shell level, and it'll work for any command.while read server; do  ssh $server uname -a </dev/nulldone < /home/kenny/list_of_servers.txtA tempting method to avoid ssh's input coming from the file is to put the redirection on the read command: while read server </home/kenny/list_of_servers.txt; do . This will not work, because it causes the file to be opened again each time the read command is executed (so it would read the first line of the file over and over). The redirection needs to be on the whole while loop so that the file is opened once for the duration of the loop.The general solution is to provide the input to the loop on a file descriptor other than standard input. The shell has constructs to ferry input and output from one descriptor number to another. Here, we open the file on file descriptor 3, and redirect the read command's standard input from file descriptor 3. The ssh client ignores open non-standard descriptors, so all is well.while read server <&3; do  ssh $server uname -adone 3</home/kenny/list_of_servers.txtIn bash, the read command has a specific option to read from a different file descriptor, so you can write read -u3 server.Related reading: File descriptors & shell scripting; When would you use an additional file descriptor?