05-27-2010
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I know the root login/password for a machines, and I want to automate some commands like this from each:
ssh root@remoteHost1 "tail /var/log/messages"
ssh root@remoteHost2 "tail /var/log/messages"
ssh root@remoteHost3 "tail /var/log/messages"
ssh root@remoteHost4 "tail /var/log/messages"
ssh... (2 Replies)
Discussion started by: jjinno
2 Replies
2. Solaris
We have a Solaris 10 server that we're migrating an old Cadre Teamwork application to. We find that when users on Sun workstations use ssh -X <username>@<new server> and run Teamwork on this new server it is fine.
When cygwin users and linux users run ssh -X to get to this new platform they... (0 Replies)
Discussion started by: pzxkys
0 Replies
3. Shell Programming and Scripting
Hey,
I'm trying to build customized behavior in a bash script for when it is run within an ssh session. This is how I'm finding out if the current session is ssh:
USER=`whoami` ... (3 Replies)
Discussion started by: neked
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
I was logged in on a server, by ssh, with a vim open, when the battery of my laptop got empty.
When I return to the server by ssh, I can see my previous ssh session still open, and the vim process running (ttyp0). Is there a way to attach that vim to my new session (ttyp4)?
Here's part... (2 Replies)
Discussion started by: raphinou
2 Replies
5. Shell Programming and Scripting
I am using Net::SSH::Expect to connect to the device(iLO) with SSH. After the $ssh->login() I'm able to view the prompt, but not able to send any coommands.
With the putty I can connect to the device and execute the commands without any issues.
Here is the sample script
my $ssh =... (0 Replies)
Discussion started by: hansini
0 Replies
6. HP-UX
Hello,
When I connect to a HP-UX 11.23 and/or 11.31 after a time without activity, the session hang.
There is not TMOUT stablished, and the session NOT finish, always keep hang after about 20min of inactivity period.
Anyone knows if this problem is related to HP-UX or network... (1 Reply)
Discussion started by: RuBiCK
1 Replies
7. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
8. Shell Programming and Scripting
Hi,
I want to execute some script on the remote session and transfer the processed file on remote machine to local machine.
I tried with ssh-keygen and ssh-copy-id but seems that this has been disable on the remote machines,
Is there any possiblity that I can save the remote username and... (7 Replies)
Discussion started by: maruthavanan
7 Replies
9. Shell Programming and Scripting
Is it possible to ssh to a server in perl and execute multiple commands without doing them all at once?
I know I can potentially do something like
system( 'ssh user@server "cd directory; grep blah *; curl someurl.com"');
However, I'd like the functionality where I don't have to keep SSHing... (3 Replies)
Discussion started by: mrwatkin
3 Replies
10. Shell Programming and Scripting
Hi ,
I am running a script on multiple servers.When I run that script on one server,I want to exit from that server and want to go to next server.PFB script:
Suppose there are 3 servers:server1,server2,server3.I am currently in server1.
for h in {2..3}
do
ssh username@server$h <<EOF
... (4 Replies)
Discussion started by: sonu141
4 Replies
QSTAT(1) User Contributed Perl Documentation QSTAT(1)
NAME
qstat - display job/partition information in a familiar pbs format
SYNOPSIS
qstat [-f] [-a|-i|-r] [-n [-1]] [-G|-M] [-u user_list] [-? | --help] [--man] [job_id...]
qstat -Q [-f]
qstat -q
DESCRIPTION
The qstat command displays information about jobs.
OPTIONS
-a Displays all jobs in a single-line format. See the STANDARD OUTPUT section for format details.
-i Displays information about idle jobs. This includes jobs which are queued or held.
-f Displays the full information for each selected job in a multi-line format. See the STANDARD OUTPUT section for format details.
-G Display size information in gigabytes.
-M Show size information, disk or memory in mega-words. A word is considered to be 8 bytes.
-n Displays nodes allocated to a job in addition to the basic information.
-1 In combination with -n, the -1 option puts all of the nodes on the same line as the job id.
-r Displays information about running jobs. This includes jobs which are running or suspended.
-u user_list
Display job information for all jobs owned by the specified user(s). The format of user_list is: user_name[,user_name...].
-? | --help
brief help message
--man
full documentation
STANDARD OUTPUT
Displaying Job Status
If the -a, -i, -f, -r, -u, -n, -G, and -M options are not specified, the brief single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job name
the job owner
the cpu time used
the job state
C - Job is completed after having run E - Job is exiting after having run. H - Job is held. Q - job is queued, eligible to run or
routed. R - job is running. T - job is being moved to new location. W - job is waiting for its execution time (-a option) to be
reached. S - job is suspended.
the queue that the job is in
If the -f option is specified, the multi-line display format is used. The output for each job consists of the header line: Job Id: job
identifier followed by one line per job attribute of the form: attribute_name = value
If any of the options -a, -i, -r, -u, -n, -G or -M are specified, the normal single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job owner
the queue the job is in
the job name
the session id (if the job is running)
the number of nodes requested by the job
the number of cpus or tasks requested by the job
the amount of memory requested by the job
either the cpu time, if specified, or wall time requested by the job, (in hh:mm)
the job state
The amount of cpu time or wall time used by the job (in hh:mm)
EXIT STATUS
On success, qstat will exit with a value of zero. On failure, qstat will exit with a value greater than zero.
perl v5.14.2 2012-04-10 QSTAT(1)