Search Results

It's the tar file. I didn't expect a tarball made on linux to be fed to a solaris system. Here are modified instructions for creating a tarball in linux that ought to work on Solaris:

mkdir...

It runs two commands on the remote server.

1) mkdir /remote/path/$ENV/whatever
2) tar -C /remote/path/$ENV/whatever -xf - < ~/file.tar

They are separated by ';', which will be fed into the...

It's also possible to send an entire remote script into ssh, however:

ssh username@host exec /bin/bash -s "argument1" "argument2" < local-file.sh

Which is about equivalent to ./local-file.sh...

You can't run local functions on a remote server. ssh doesn't work that way. The other side is a brand-new, independent shell, not an extension of your own. It may not even be the same shell.
...

Yeah... calling ssh 300 times, to do 300 mkdir calls is a bit of a waste.

Instead of hardcoding all the paths in the script, I'd make a tarball. That will preserve permissions and let you bundle...

Unless this mkproj_dir program actually exists on the remote server, it can't run it on the remote server. This is why I demonstrated using shell commands over ssh, not running a remote script.
...

How about something like this?

mkproj_dirs() {
mkdir -p "$1"
cd "$1" &&
mkdir archivefiles dropbox logfiles lookupfiles maestro parameterfiles rejectfiles scriptfiles sqlfiles...

Show me exactly what you typed, please, as well as the values of the variables involved. Leaving out any of the punctuation I gave will cause it to fail, since that's what causes ssh to do multiple...