Although I answered the question that was asked, I always do as methyl suggests for any remote commands beyond a simple "uptime" or "date".
I do sometimes type in loops or quick function definitions at the command line locally as I showed in my example. So I stay up to speed on ksh syntax as well. Real example: I was on a broken system and cat and ls didn't work, nor did most commands. So I do a quick:
and I can look around with commands like "myls /etc/*" and "mycat somefile". It's very handy being able to pull stuff like that out of my hat when I need to.
Help!
I'm would like to log in su - within a script an contuine to run the commands within the script. Every time I log in as su - I have to exit for the rest of the script to run! e.g.
#!/bin/ksh
su - oracle
ps -ef |grep som <--- doesn't excute command until I log out su
oracle.... (1 Reply)
Hi folks,
I have the following configuration file:
DB_LAYER=NO
ADMIN_LAYER=NO
RTESUB_LAYER=NO
DB_HOST_NAME=tornado
ADMIN_HOST_NAME=tornado
RTESUB_HOST_NAME=tornado
RESPONSE_FILE_SR=/tmp/SR.rsp
INSTALL_SR_1=/home/Upgrade_4.7.1/Utilities/Install_SR:Y... (8 Replies)
Hi,
In ksh how can I execute something like this:
remsh newhost "for i in 1 2 3 4 5 do echo file$i; cat file$i; done"
I cannot pass the contrl J or enter in th above line which is required by the for loop.
Thanks... (1 Reply)
I have a space delimited file containing: hostname OracleSID connectstring
I want to loop through the file and execute remsh to check the database processes.
cat $filename | while read HOST SID CONNECT
do
{
result=`remsh $HOST "ps -ef | grep pmon_${SID}$| grep -v grep"`
if ........ (1 Reply)
Boy I hope someone can answer this question. I've been beating my head against the wall all day trying to come up with a solution.
I have a carrot delimited file that looks like this:
ANDERSON^678934^1974^BOB
JONES^564564345^1954^ABRAHAM
SMITH^47568465^1948^JON
If I run this command:
awk... (6 Replies)
Sorry for such a dreadful title, but I'm not sure how to be more descriptive. I'm hoping some of the more gurutastic out there can take a look at a solution I came up with to a problem, and advice if there are better ways to have gone about it.
To make a long story short around 20K pieces of... (2 Replies)
I have the below code which runs on multiple databases , but this runs one-after-one. I will need this to run in parallel so that i could save a lot of time. Please help!!! Thanks in advance
for Db in `cat /var/opt/oracle/oratab |egrep -v "ASM" |grep -v \# |cut -d\: -f1`
do
{
export... (5 Replies)
OS : RHEL 6.1
Shell : Bash
I had a similair post on this a few weeks back. But I didn't explain my requirements clearly then. Hence starting a new thread now.
I have lots of files in /tmp/stage directory as show below.
I want to loop through each files to run a command on each file.
I... (8 Replies)
Discussion started by: kraljic
8 Replies
LEARN ABOUT OPENSOLARIS
echo
echo(1B) SunOS/BSD Compatibility Package Commands echo(1B)NAME
echo - echo arguments to standard output
SYNOPSIS
/usr/ucb/echo [-n] [argument]
DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.
echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
ronment variables.
For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:
o echo your current-working-directory's full pathname
o pipe the output through tr to translate the path's embedded slash-characters into space-characters
o pipe that output through wc -w for a count of the names in your path.
example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"
See tr(1) and wc(1) for their functionality.
The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if
the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's
echo() also understands a as the audible bell character; however, these commands do not have an -n option.
OPTIONS -n Do not add the NEWLINE to the output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases.
SunOS 5.11 3 Aug 1994 echo(1B)