That would call the function locally, and feed its output into ssh.

Still, you cannot, since functions aren't exported across ssh calls. It's like running a fresh script. It knows nothing about your functions or environment...

Yes. You won't be able to use standard input for anything else, though. It means what it says. stdin is not a terminal, it's a here-document, so it doesn't allocate a pseudo-tty.

Other than that, there's nothing wrong with it. Nothing's actually going wrong. The shell's just complaining since its input isn't an interactive terminal. They're not errors, they're warnings.

I think you can avoid the warnings by running the shell in a manner so it doesn't expect stdin to be a terminal.

Code:

ssh username@host /bin/sh -s <<EOF
...
EOF

If you want the deluxe version, the one I tend to use:

Code:

ssh username@host exec /usr/bin/env sh -s "arg1" "arg2" "arg3" <<"EOF"
echo "First argument is $1"
echo "Second argument is $2"
echo "Third argument is $3"
EOF

Running sh in this way should be quite safe, and using <<"EOF" makes sure nothing gets substituted into the here document, no substitution at all. The only way you can transfer in variables is with the "arg1" "arg2" "arg3" there, which become $1 $2 $3 ...