Do you know how long the commands on the remote machine will approximately take? If so you could run the ssh-command in the background and then use sleep to let pass this time (plus some for contingency). If the command the still runs, you consider it to be hanging and kill it, if it has finished it is ok. You can use the "jobs" built-in ksh command to check the status of the job.
We suppose the commands you want to run remotely will take 20 seconds approximately. We add 10 seconds just to be sure and put the IP adress of the host to be contacted in a variable which is read in a loop :
The first "jobs" statement is there to clear the display of all the "done"-messages if backgroup jobs already terminated during the sleep-statement.
bakunin
thank you so much Bakunin, will try this code and let you know the results.
But I am not very sure about the ksh shell.
Thanks a TON !!
Last edited by vikas027; 11-04-2007 at 09:26 PM..
Reason: forgot something
We have a unix script scheduled to execute once in a day, some times it hangs on the server and never performs its operations, we need to manually kill the process and re-start that script, is there any way to have notification when the script hangs on the server.
Thanks & Regards,
Murthy. (3 Replies)
Hi,
Im creating a script that is supposed to run commands on remote server using sftp.
My script is as below:
#!/bin/ksh
sftp remote_server
mypassword
cd /u08/mydir/allfiles
mget *
..
But this is what I got when I runned the script:
Connecting to remote server...... (3 Replies)
Hi, I have googled for quite some time and couldn't able to get what exactly I am looking for.. My query is "how to stop a shell script which is running inside a remote server, using a script"??? can any one give some suggestions to sort this out. (1 Reply)
Hi All,
I am using a expect script to run a shell script on remote server, the code is as follows. But the problem is that it executes only first command, and hangs it doesn't run the next commands.
spawn ssh $uid@$host
expect "password:"
send "$password\r"
expect "*\r"
send... (2 Replies)
hi,
I am using the below line to run a script from remote server(say server A) to another server(say server B).
ssh username@servername ksh script name.
The issue is the script logs into server B, executes the script on server B, transfers the file to server A but does not exit from... (4 Replies)
Hi,
I am trying to automate the process of fetching files from remote server to local server through sftp. I have the username and password for the remote solaris server. But I need to give password manually everytime i run the script.
Can anyone help me in automating the script such that it... (3 Replies)
Hi guys,
So i am in server1 and i have to login to server 2, 3,4 and run some script there(logging script) and output its result. What i am doing is running the script in server2 and outputting it to a file in server 2 and then Scp'ing the file to server1. Similarly i am doing this for other... (5 Replies)
Hello Every one!!
I am trying to write a shell script which will connect to a remote server and execute scripts which are at a certain path in the remote server.
Before this I am using a sudo command to change the user.
The place where I am stuck is, I am able to connect to the... (6 Replies)
I have a script, which connecting to remote server and first checks, if the files are there by timestamp. If not I want the script exit without error. Below is a code
TARFILE=${NAME}.tar
TARGZFILE=${NAME}.tar.gz
ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;... (3 Replies)
local script:
cat > first.sh
cd /tmp
echo $PWD
echo `whoami`
cd /tmp/123
tar -cvf 789.tar 456
sleep 10
except script:
cat > first
#!/usr/bin/expect
set ip 10.5.15.20
set user "xyz123"
set password "123456"
set script first.sh
spawn sh -c "ssh $user@$ip bash < $script" (1 Reply)
Discussion started by: Aditya Avanth
1 Replies
LEARN ABOUT OSF1
jobs
jobs(1) General Commands Manual jobs(1)NAME
jobs - Displays status of jobs in the current session
SYNOPSIS
jobs [-l | -p] job_id...
[Tru64 UNIX] jobs [-n] job_id...
Note
The C shell has a built-in version of the jobs command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/jobs. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
jobs: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Provides more information about each job listed. This information includes the job number, current job, process group ID, state and the
command that formed the job. Displays only the process IDs for the process group leaders of the selected jobs. [Tru64 UNIX] Displays
jobs that have stopped or exited since last notified.
By default, the jobs utility displays the status of all stopped jobs, running background jobs and all jobs whose status has changed and has
not been reported by the shell.
OPERANDS
Specifies the jobs for which the status is to be displayed. If no job_id operand is given, the status information for all jobs is dis-
played. The format of job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
The jobs utility displays the status of jobs that were started in the current shell environment.
When jobs reports the termination status of a job, the shell removes its process ID from the list of those "known in the current shell exe-
cution environment". See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
The jobs utility does not work as expected when it is operating in its own utility execution environment because that environment has no
applicable jobs to manipulate.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of jobs: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error and informative messages written to standard output.
Determines the location of message catalogues for the processing of LC_MESSAGES.
SEE ALSO
Commands: bg(1), csh(1), fg(1), kill(1), ksh(1), sh(1p), wait(1)
Standards: standards(5)jobs(1)