-systemsboy

echo “Enter User Name and press return…”
read username

ssh -t user@localhost “ls ~$username”

This will work just fine! You need to use double quotes to tell bash to interpolate variables. Your code actually helped me figure this out, since you use single quotes in the first [non-working] example and double quotes in the second [working] example.

You can either log in to each machine 1-at-a-time, or you can use a for or while loop to automate the process, as per the comments in this article:
http://systemsboy.blogspot.com/2006/07/send-remote-commands-via-ssh.html

-systemsboy

From Chile

Thanks!

-systemsboy

Here’s a simple two liner for yah:
echo -n “Username: ” && read username
ssh -t root@remote.site “ls ~${username}”

what happens here is when you put a variable name within ${} instead of just a $var_name the shell expands it, like hitting tab on the cli or echoing the values. This is not only useful in this case but also if you have ANSI colors, or values returned from a command.

It seemes the ssh messes with the stdin and halted our while statement.

Try setting -n on the ssh options. It worked for us.

I am having some serious dificulties regarding a ssh runing remote script a sent by a local script in the midle of a loop:

#!/bin/bash
while [statement]; do
yada; yada; yada;
if [statement]; then
ssh -p xxxx $USER@$HOST `remote_script.sh`
fi
yada; yada; yada;
done

The thing is, even if the while has many things else to do, the first time it runs the remote script (or command) via ssh, the while exits with no particular reazon.

It does not matter if the remote commands ends up successfully or not.

Is there any mandatory “DROP ALL LOOPS” after any SSH sort of undocumented “feature”?

The real bizzar portion is, that if I force the remote script to run on the backgrounf with a & like this:

#!/bin/bash
while [statement]; do
yada; yada; yada;
if [statement]; then
ssh -p xxxx $USER@$HOST `remote_script.sh &`
fi
yada; yada; yada;
done

…it goes on, but the remote_script.sh is supposed to run serialized and never in paralel with another instance of it self, therefore crasing.

Thanx in advance.

ssh -t user@host ‘passwd username’

-systemsboy