12-28-2008
Okay, I fiddled some more and I think that the problem is actually that since I'm using a here document, it's reading the lines of the doc off to the remote box as if they were individual commands instead of pieces of a script.
So I guess what i need is a way to get the remote box to have the lines interpreted as a shell script instead of individual commands.
Any thoughts?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a solaris9 x86 server using ssh as follows:
SSH Version Sun_SSH_1.0, protocol versions 1.5/2.0.
The remote server solaris9 sparc has exactly the same version ssh installed.
I am running a script on my server which includes the following command to run a script on the remote server:... (4 Replies)
Discussion started by: frustrated1
4 Replies
2. AIX
dears
i have two IBM p630 application servers, they are running hacmp 5.2 as the clustering software.
from the output of errpt on one of the nodes i am receiving the following error:
9D30B78E 0530020007 T S tty1 RECEIVER OVER-RUN ON INPUT
please are there any ideas about how... (0 Replies)
Discussion started by: TheEngineer
0 Replies
3. OS X (Apple)
Hi all,
we are just confused about a strange problem on one server in production (XServer, running OSXS 10.5.6). It works normal for month. Since two day everthing seems to be fine also with one exception.
When we connect trough ssh we won't get a tty session. For testing purposes, we enabled... (2 Replies)
Discussion started by: Frank.Knobloch
2 Replies
4. Shell Programming and Scripting
I want to use ssh to start a bash script that I have uploaded to a webhost. How do I do that from linux? (2 Replies)
Discussion started by: locoroco
2 Replies
5. Shell Programming and Scripting
Hi Team,
I am trying to run shell script from one server to another server with below command.
ssh abc@pqr.america.com /tmp/test.ksh
But, it gives below error. Can someone help me what is the issue?
exec(): 0509-036 Cannot load program ssh because of the following errors:
... (3 Replies)
Discussion started by: ace_friends22
3 Replies
6. Shell Programming and Scripting
Hello
when try to excute the following
ssh -l pla 10.287.60.55 vis_fil
vis_fil not found.
but it works fine when login to the server.
can you help me run this command in one online because i will add later to shell script
regards (1 Reply)
Discussion started by: mogabr
1 Replies
7. UNIX for Advanced & Expert Users
Scenario:
I would like the ability to be able to use the cli on a client that has remotely connected to me via my ssh server in my office and use their terminal to work remotely if I am in another remote location.
Ex.
The client reverse ssh's to my remote ssh server in my office.
ssh... (5 Replies)
Discussion started by: metallica1973
5 Replies
8. Shell Programming and Scripting
Hi all,
I have the following Perl script which is intended to run a Shell script and generate some logging for the purposes of tracking weather or not the script ran.
I get an error, of course, since I don't know what I'm doing really.
Here is the code:
#!/opt/perl/bin/perl -w
... (14 Replies)
Discussion started by: zixzix01
14 Replies
9. Shell Programming and Scripting
If I execute below code I am able to get string from column8 and column10 about a process.
serverA1$> ps -ef | grep rotate | grep 'config' | awk '{print $8" "$10}'
/<Oracle_home>/ohs/bin/odl_rotatelogs -h:/<app_Home>/config/OHS/ohs1/component_events.xml_ohs1... (12 Replies)
Discussion started by: kchinnam
12 Replies
10. Shell Programming and Scripting
Hi,
I'm facing issues while trying to run a sample program on Linux.
If I try to run the script using the command "sh <filename.prog>", it doesn't work. But, if I try to execute it using the command "ksh <filename.prog>", it works fine.
Even ". ./filename.prog" works fine.
Can you... (6 Replies)
Discussion started by: venkatesh17
6 Replies
scotty(1) Tnm Tcl Extension scotty(1)
__________________________________________________________________________________________________________________________________________________
NAME
scotty - A Tcl shell including the Tnm extensions.
SYNOPSIS
scotty ?fileName arg arg ...?
_________________________________________________________________
DESCRIPTION
scotty is a Tcl interpreter with extensions to obtain status and configuration information about TCP/IP networks. After startup, scotty
evaluates the commands stored in .scottyrc and .tclshrc in the home directory of the user.
SCRIPT FILES
If scotty is invoked with arguments then the first argument is the name of a script file and any additional arguments are made available to
the script as variables (see below). Instead of reading commands from standard input scotty will read Tcl commands from the named file;
scotty will exit when it reaches the end of the file.
If you create a Tcl script in a file whose first line is
#!/usr/local/bin/scotty2.1.11
then you can invoke the script file directly from your shell if you mark the file as executable. This assumes that scotty has been
installed in the default location in /usr/local/bin; if it's installed somewhere else then you'll have to modify the above line to match.
Many UNIX systems do not allow the #! line to exceed about 30 characters in length, so be sure that the scotty executable can be accessed
with a short file name.
An even better approach is to start your script files with the following three lines:
#!/bin/sh
# the next line restarts using scotty
exec scotty2.1.11 "$0" "$@"
This approach has three advantages over the approach in the previous paragraph. First, the location of the scotty binary doesn't have to
be hard-wired into the script: it can be anywhere in your shell search path. Second, it gets around the 30-character file name limit in
the previous approach. Third, this approach will work even if scotty is itself a shell script (this is done on some systems in order to
handle multiple architectures or operating systems: the scotty script selects one of several binaries to run). The three lines cause both
sh and scotty to process the script, but the exec is only executed by sh. sh processes the script first; it treats the second line as a
comment and executes the third line. The exec statement cause the shell to stop processing and instead to start up scotty to reprocess the
entire script. When scotty starts up, it treats all three lines as comments, since the backslash at the end of the second line causes the
third line to be treated as part of the comment on the second line.
VARIABLES
Scotty sets the following Tcl variables:
argc Contains a count of the number of arg arguments (0 if none), not including the name of the script file.
argv Contains a Tcl list whose elements are the arg arguments, in order, or an empty string if there are no arg arguments.
argv0 Contains fileName if it was specified. Otherwise, contains the name by which scotty was invoked.
tcl_interactive Contains 1 if scotty is running interactively (no fileName was specified and standard input is a terminal-like device), 0
otherwise.
PROMPTS
When scotty is invoked interactively it normally prompts for each command with ``% ''. You can change the prompt by setting the variables
tcl_prompt1 and tcl_prompt2. If variable tcl_prompt1 exists then it must consist of a Tcl script to output a prompt; instead of out-
putting a prompt scotty will evaluate the script in tcl_prompt1. The variable tcl_prompt2 is used in a similar way when a newline is typed
but the current command isn't yet complete; if tcl_prompt2 isn't set then no prompt is output for incomplete commands.
SEE ALSO
Tnm(n), Tcl(n)
AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl>
Tnm scotty(1)