09-14-2010
Quote:
I use ssh in script to access various systems (solaris, hp-ux, linux...) if I want remote use ifconfig somewhere it works somewhere not.
- I found that that may be the PATH problem or something with sourcing and variables - I am not familiar with it and I am a little bit confused, but anyway it is recommend to use /sbin/ifconfig (as you did)
OK but what if somewhere is ifconfig in another path ? Is possible to use classic ifconfig in script?
No, as far as I know,
ifconfig's position and syntax varies accross different operating systems,
so I would suggest to use a custom code for your environment.
Quote:
- Second problem: Is possible to remote use bash script for loop on system which did not have bash ? Example is more than 1000 words:
[...]
The commented line in above code works if it is not in bash script
Could you post the exact error message or explain what you mean by "not working"?
Quote:
- Third problem: Is good practice to set environment variables when I log on server via script (to avoid expecting input) ? Is it necessary for script to have set environment variables or is there any better solution ?
Code:
ssh server "DISPLAY=:0; TERM=xterm; /sbin/ifconfig -a" | grep -v 127.0.0.1 | grep 'inet addr'
I'm not sure about this one. Some ssh client implementations support the -t/-T switch to enable/disable pseudo-tty allocation,
I don't know if setting the above mentioned variables has some impact.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi unix guru's
i am new to unix shell programming.
i found a trouble in executing a script(bali.ksh) which is available on serverA with username xyza, this script contains sqlplus command to retrive the data from the database available on other serverC.
Now i need to run the above script... (4 Replies)
Discussion started by: balireddy_77
4 Replies
2. Shell Programming and Scripting
Does anyone know how to execute remote script asynchronously?
Here is my command
TargetList=$testmaker/config/prod_domain.list
for targethost in `cat $TargetList`; do
rsh $targethost -l bvuser "$HOME/var/script-root/afp/bin/run_nrtp_cache_flush.sh $appName"
done (1 Reply)
Discussion started by: leemjesse
1 Replies
3. Shell Programming and Scripting
Help please!!
I want to use ssh to execute a remote exe and while it's running I want to query for the process ID of the exe (2 different ssh commands)
1. sshpass -p "<passwd>" ssh -f -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@<ipaddress> nohup /tmp/mmds_asyn &
2.... (0 Replies)
Discussion started by: rvompoluTMW
0 Replies
4. Windows & DOS: Issues & Discussions
Hi all,
I'm not sure if it is correct to post here.
I am facing problem wanting to create a batch that run from my Windows XP pc to remote to multiple Solaris server to execute the server's ksh script. :wall:
Can anyone give me a hints on how to do that? Thanks. (6 Replies)
Discussion started by: beginningDBA
6 Replies
5. Shell Programming and Scripting
Hi,
I am new to the expect scripting.
I have this expect script as below :
spawn ssh remote_server -l id
set pass "12345"
set opt "s"
expect "Password:" {send "$pass\r" ; }
expect "*ENTER*" {send "Enter\r"; exp_continue }
expect "Please select option :" {send... (2 Replies)
Discussion started by: curt137
2 Replies
6. IP Networking
So, is there way of automating this ?
My ultimate goal is to run some cmd script in windows and it should connect to a remote unix host and run a script x.sh located on the remote unix host.
I was wanting to achieve this by using WinSCP and Putty only. If possible let me know how and if not... (25 Replies)
Discussion started by: mohtashims
25 Replies
7. Shell Programming and Scripting
I am unable to run the below script against a remote server due to syntax error (then unexpected), but i am able to run it locally. Am i executing it correctly or is there any other way to execute it.
ssh username@servernname ksh -s < scriptname
#!/bin/ksh
function record
{
((end =... (5 Replies)
Discussion started by: NarayanaPrakash
5 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
We have 2 servers A and B.
B is having a sctipt called b.sh in path /home/dev/scripts.
Now my requirement is i want to execute b.sh from server A.
Kindly help me. (3 Replies)
Discussion started by: Girish19
3 Replies
9. Shell Programming and Scripting
Hi,
The below command is not giving me the count , Can somebody help me in re-writing this pls .
Proc_Exist=`ssh -q -o "BatchMode=yes" -o "PasswordAuthentication=no" $OAUSER@${Primary_Node} ps -ef |
grep -v grep | grep "${ICM_Proc}" |wc -l `
Also the same problem with below... (13 Replies)
Discussion started by: Y.balakrishna
13 Replies
10. Shell Programming and Scripting
I want to execute a shell script(set of commands) on remote machine and that script takes input from text file(local machine). Please refer below:
ssh user@hostname 'bash -s'< ./test.sh file.txt
But i got the error file.txt doesn't exist.
Can anyone help me on this.
Content of test.sh:
... (2 Replies)
Discussion started by: manishtri88
2 Replies
RECON(1) LAM TOOLS RECON(1)
NAME
recon - Check if LAM can be started.
SYNTAX
recon [-abdhv] [<bhost>]
OPTIONS
-a Report all host errors.
-b Assume local and remote shell are the same. This means that only one remote shell invocation is used to each node. If -b is not
used, two remote shell invocations are used to each node.
-d Turn on debugging.
-h Print the command help menu.
-v Be verbose.
DESCRIPTION
In order for LAM to be started on a remote UNIX machine, several requirements have to be fulfilled:
1) The machine must be reachable via the network.
2) The user must be able to remotely execute on the machine with the default remote shell program that was chosen when LAM was config-
ured. This is usually rsh(1), but any remote shell program is acceptable (such as ssh(1), etc.). Note that remote host permission
must be configured such that the remote shell program will not ask for a password when a command is invoked on remote host.
3) The remote user's shell must have a search path that will locate LAM executables.
4) The remote shell's startup file must not print anything to standard error when invoked non-interactively.
If any of these requirements is not met for any machine declared in <bhost>, LAM will not be able to start. By running recon first, the
user will be able to quickly identify and correct problems in the setup that would inhibit LAM from starting.
The local machine where recon is invoked must be one of the machines specified in <bhost>.
The <bhost> file is a LAM boot schema written in the host file syntax. See bhost(5). Instead of the command line, a boot schema can be
specified in the LAMBHOST environment variable. Otherwise a default file, bhost.def, is used. LAM seaches for <bhost> first in the local
directory and then in the installation directory under etc/.
recon tests each machine defined in <bhost> by attempting to execute on it the tkill(1) command using its "pretend" option (no action is
taken). This test, if successful, indicates that all the requirements listed above are met, and thus LAM can be started on the machine.
If the attempt is successful, the next machine is checked. In case the attempt fails, a descriptive error message is displayed and recon
stops unless the -a option is used, in which case recon continues checking the remaining machines.
If recon takes a long time to finish successfully, this will be a good indication to the user that the LAM system to be started has slow
communication links or heavily loaded machines, and it might be preferable to exclude or replace some of the machines in the system.
Remote shell invocation
Note that the default remote shell command can be overriden at invocation time with the LAMRSH environment variable. The LAMRSH environ-
ment variable can be set with a new command and optional command line arguments. For example, the 1.x series of ssh clients require the -x
flag to be specified to suppress standard ssh information from being sent to the standard error (which would cause recon to fail). For
example (for the C shell and its derrivates):
setenv LAMRSH "ssh -x"
Normally, recon uses two remote shell invocations to each node. The first remote shell invocation is used to determine the user's shell on
the remote node. The second remote shell invocation is used to launch the desired LAM binary on the remote node. If the -b switch is
used, recon will assume that the user's shell on all remote nodes is the same as it is on the local node, and therefore only one remote
shell invocation is used, which is noticably faster.
In either case, on remote nodes, if the user's shell is not csh, tcsh, or bash, .profile is invoked by LAM before invoking any LAM binary.
This allows the user to setup paths and any necessary environment before LAM binaries are invoked (csh and tcsh users can put such setup in
their $HOME/.cshrc or $HOME/.tcshrc files; bash users can put this setup in their $HOME/.bashrc file).
FILES
$LAMHOME/etc/lam-bhost.def default boot schema file
EXAMPLES
recon -v mynodes
Check if LAM can be started on all the UNIX machines described in the boot schema mynodes. Report about important steps as they are
done.
recon -v -a
Check if LAM can be started on all the UNIX machines described in the default boot schema. Report about important steps as they are
done. Check all the machines; do not stop after the first error message.
SEE ALSO
rsh(1), tkill(1), bhost(5), lamboot(1), wipe(1), lam-helpfile(5)
LAM 6.5.8 November, 2002 RECON(1)