Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Running local script remotely with arguments Post 303030713 by MadeInGermany on Thursday 14th of February 2019 01:00:02 PM
Old 02-14-2019
Yes, with ssh the argument strings are dequoted by the local shell and then seen by the remote shell. The "$@" or a "${array[@]}" only preserves the strings for the local dequoting.
The args=$(printf "%q " "$@") \escapes each special character, so the double dequoting works.
Other methods are args=$(printf "'%s' " "$@") or args=$(printf "\"%s\" " "$@").
This User Gave Thanks to MadeInGermany For This Post:
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

running command remotely to populate local variable

If I run this # ssh remote-server 'du -sk /usr/platform/`uname -i`/' 174 /usr/platform/SUNW,Sun-Fire-V245 I get my output just fine, However, if i try to do the same but populate a local variable within my script called for example 'result' #!/bin/ksh result=`ssh remote-server... (3 Replies)
Discussion started by: hcclnoodles
3 Replies

2. Shell Programming and Scripting

remotely call function from local script

The following code doesn't work properly which means it doesn't displays remote output. #!/bin/ksh #################### Function macAddressFinder ######################## macAddressFinder() { `ifconfig -a > ipInterfaces` `cat ipInterfaces` }... (2 Replies)
Discussion started by: presul
2 Replies

3. Solaris

Can i bind to a local login terminal running using rsh or remotely

Hi Can i ask? I had multiple solaris workstation running and some local users using it. Is it possible to bind to the local user terminal or console he's using as if like the user well type and I can see it and what my typing in the local user see it also. Is it possible.. Thanks. (3 Replies)
Discussion started by: jao_madn
3 Replies

4. Shell Programming and Scripting

Running local script remotely with arguments in ksh

When i use ssh command to execute local script on remote server , I am unable to do it. Please let me know how this can be done in ksh req=abc dte=ghd ssh username@hostname "$req $dte" < run_script.sh (2 Replies)
Discussion started by: lalitpct
2 Replies

5. Shell Programming and Scripting

Then error while running script remotely

facing issue with then error while running a local script aginst a remote server. i facing the same issue in multiple scripts. So what i am missing here or what is needed. #!/bin/ksh echo "enter the filename" read file if then echo "file exists" else echo "file does not exists" fi ... (0 Replies)
Discussion started by: NarayanaPrakash
0 Replies

6. Shell Programming and Scripting

To run a local shell script in a remote machine by passing arguments to the local shell script

I need to run a local shell script on a remote machine. I am able to achieve that by executing the command > ssh -qtt user@host < test.sh However, when I try to pass arguments to test.sh it fails. Any pointers would be appreciated. (7 Replies)
Discussion started by: Sree10
7 Replies

7. Shell Programming and Scripting

Passing arguments while running the script

Hi, I have a requirement for creating a MQ (queue) where the inputs has to be passed as arguments. Running the script as below ./hi.sh "Servername" "QueueManagername" "QueuecreationCommand" cat hi.sh echo "Welcome to $1" runmqsc $2 < $3 But the queue creation command is... (9 Replies)
Discussion started by: Anusha M
9 Replies

8. Shell Programming and Scripting

Difference between running a script locally and remotely

Hello, Please, what is the difference between running a script remotely: ssh -t root@$machine -x "sshpass -p 'ubuntu' ssh -t ubuntu@$address -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/nul -x './c-launch.sh'" and running a script directly on the host: ... (1 Reply)
Discussion started by: chercheur111
1 Replies

9. Shell Programming and Scripting

How can I execute local script on remote machine and include arguments?

I have a script in local server cd /home/dell/work/BOP/testdir ./processchk po (here processchk is a script & po is passed as an argument) Now I want to execute this script from remote server ssh $username@$hostname "cd /home/dell/work/BOP/testdir; ./processchk po" But Its getting error... (9 Replies)
Discussion started by: manohar2013
9 Replies

10. Shell Programming and Scripting

Need to pass arguments while running a Shell Script

Shell Script Gurus, I am writing a shell script which needs User ID's to pass as an Arguments in command line while executing. Can this be doable? I've never done this, If you give a sample script that would be helpful, Thanks. (1 Reply)
Discussion started by: shekar777
1 Replies
getopts(1)						      General Commands Manual							getopts(1)

NAME
getopts - parse utility (command) options SYNOPSIS
optstring name [arg ...] DESCRIPTION
is used to retrieve options and option-arguments from a list of parameters. Each time it is invoked, places the value of the next option in the shell variable specified by the operand and the index of the next argu- ment to be processed in the shell variable Whenever the shell is invoked, is initialized to 1. When the option requires an option-argument, places it in the shell variable If no option was found, or if the option that was found does not have an option-argument, is unset. If an option character not contained in the optstring operand is found where an option character is expected, the shell variable specified by name is set to the question-mark character. In this case, if the first character in optstring is a colon the shell variable is set to the option character found, but no output is written to standard error; otherwise, the shell variable is unset and a diagnostic message is written to standard error. This condition is considered to be an error detected in the way arguments were presented to the invoking appli- cation, but is not an error in processing. If an option-argument is missing: o If the first character of optstring is a colon, the shell variable specified by name is set to the colon character and the shell variable is set to the option character found. o Otherwise, the shell variable specified by name is set to the question-mark character, the shell variable is unset, and a diag- nostic message is written to the standard error. This condition is considered to be an error detected in the way arguments are presented to the invoking application, but is not an error in processing; a diagnostic message is written as stated, but the exit status is zero. When the end of options is encountered, exits with a return value greater than zero. The shell variable is set to the index of the first nonoption-argument, where the first argument is considered to be an option argument if there are no other non-option arguments appearing before it, or the value + 1 if there are no nonoption-arguments; the name variable is set to the question-mark character. Any of the fol- lowing identifies the end of options: the special option finding an argument that does not begin with a or encountering an error. The shell variables and are local to the caller of and are not exported by default. The shell variable specified by the name operand, and affect the current shell execution environment. Operands The following operands are supported: optstring A string containing the option characters recognized by the utility invoking If a character is followed by a colon the option will be expected to have an argument, which should be supplied as a separate argument. Applications should specify an option character and its option-argument as separate arguments, but will interpret the characters following an option character requiring arguments as an argument whether or not this is done. An explicit null option-argument need not be recognised if it is not supplied as a separate argument when is invoked. The characters question-mark and colon must not be used as option characters by an application. The use of other option characters that are not alphanumeric produces unspecified results. If the option-argument is not supplied as a separate argu- ment from the option character, the value in will be stripped of the option character and the The first character in optstring will determine how will behave if an option character is not known or an option-argument is missing. name The name of a shell variable that is set by to the option character that was found. by default parses positional parameters passed to the invoking shell procedures. If args are given, they are parsed instead of the posi- tional parameters. EXTERNAL INFLUENCES
Environment Variable The following environment variable affects the execution of the utility: Used by as the index of the next argument to be processed. ERRORS
Whenever an error is detected and the first character in the optstring operand is not a colon a diagnostic message will be written to stan- dard error with the following information in an unspecified format: o The invoking program name will be identified in the message. The invoking program name will be the value of the shell special parameter 0 at the time the utility is invoked. A name equivalent to: may be used. o If an option is found that was not specified in optstring, this error will be identified and the invalid option character will be identified in the message. o If an option requiring an option-argument is found, but an option-argument is not found, this error will be identified and the invalid option character will be identified in the message. EXAMPLES
Since affects the current shell execution environment, it is generally provided as a shell regular built-in. If it is called in a subshell or separate utility execution environment such as one of the following: it does not affect the shell variables in the caller's environment. Note that shell functions share with the calling shell even though the positional parameters are changed. Functions that use to parse their arguments should save the value of on entry and restore it before returning. However, there will be cases when a function must change for the calling shell. The following example script parses and displays its arguments: aflag= bflag= while getopts ab: name do case $name in a) aflag=1;; b) bflag=1 bval="$OPTARG";; ?) printf "Usage: %s: [-a] [-b value] args " $0 exit 2;; esac done if [ ! -z "$aflag" ] ; then printf "Option -a specified " fi if [ ! -z "$bflag" ] ; then printf "Option -b "%s" specified " "$bval" fi shift $(($OPTIND -1)) printf "Remaining arguments are: %s " "$*" SEE ALSO
getopt(1), ksh(1), sh-posix(1), sh(1), getopt(3C). STANDARDS CONFORMANCE
getopts(1)
All times are GMT -4. The time now is 10:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy