Anormally exit form bash script

could you use "ssh -n" as below;

#!/bin/bash                                                                                                                                                                                                                                                                                       
while read A; do
echo $A
ssh -n [email protected] "[[ -d /Volumes/MACBACKUP/desarrollo_backups/$A ]] || mkdir /Volumes/MACBACKUP/desarrollo_backups/$A; touch /Volumes/MACBACKUP/desarrollo_backups/$A/backup.marker" 
bash /home/vagrant/rsync_tmbackup.sh $A/ [email protected]:/Volumes/MACBACKUP/desarrollo_backups/$A/
done < cuentas.txt

man ssh ;

-n Redirects stdin from /dev/null (actually, prevents reading from stdin). This must be used when ssh is run in the background. A common trick is to use this to run X11 programs on a remote machine. For example, ssh -n shadows.cs.hut.fi emacs & will start an emacs on shadows.cs.hut.fi, and the X11 connection will be automatically forwarded over an encrypted channel. The ssh program will be put in the background. (This does not work if ssh needs to ask for a password or passphrase; see also the -f option.)

I'm pretty sure @MustafaDOGRU is right about the basic problem: when the loop starts, read reads the first line of cuentas.txt (as expected), but then something in the middle of the loop reads the rest of the file so when the script tries to read the next line... there's nothing left, and so it figures it's done and exits. Mustafa's approach was to try to figure out what part of the middle of the loop was reading and get it to stop, but it looks like there are multiple things doing it, and tracking them down may be annoying. But there's another way: pass the file's contents over something other than the standard input:

#!/bin/bash                                                                                                                                                                                                                                                                                       
while read -u3 A; do
    echo $A
    ssh [email protected] "[[ -d /Volumes/MACBACKUP/desarrollo_backups/$A ]] || mkdir /Volumes/MACBACKUP/desarrollo_backups/$A; touch /Volumes/MACBACKUP/desarrollo_backups/$A/backup.marker"
    bash /home/vagrant/rsync_tmbackup.sh $A/ [email protected]:/Volumes/MACBACKUP/desarrollo_backups/$A/
done 3< cuentas.txt

The 3< cuentas.txt directs cuentas.txt to file descriptor #3 rather than standard input (which is fd #0), and the read -u3 reads from fd #3, so those should work properly together. Since fd #3 is normally unused, the chance of anything in the middle of the loop messing with it is pretty small.