Ok I had some time to test so (changed the names of the servers so I can test...)
Code:
#!/bin/ksh
pat01=$(uname -a | awk '{printf "%s", $2}')
if [ $pat01 == 'oslo4' ] #if it is server 1 run this file
then
echo "run this file"
else
if [ $pat01 == "oslo6" ] #if it is server 2 run this file
then
echo "run the second file"
exit 2
fi
echo "Not concerned..."
exit
fi
echo "Finish"
:( :confused: Does anybody here know how to compile and run C++ programs in UNIX enviroment? I am so confused. Any help on this would be greatly appreciated! Thanks! (5 Replies)
hi,
I have one environment variable like path in my system.But in my program i need to change that path .suppose it has a value "config" now i need to chage it as "config1" or something else.i need to use that variable for complete project.It means at first it will use the old path but after... (4 Replies)
Hi,
I require need help in two aspects actually:
1) Fatal error that gets generated as %F% from a log file say ABClog.dat to trigger a mail. At present I manually grep the log file as <grep %F% ABClog.dat| cut-d "%" -f1>. The idea is to use this same logic to grep the log file which is... (1 Reply)
HI,
I have to write a unix script and need your help.
in my application where I have to invoke this script a varialble is there where the value comes in a variable . for example variable can be var=ABC
like this there will be any type of value in the vcariable.
there is a unix directory... (2 Replies)
Hi Guys,
I need to run an alias from a k-shell script ,for example 10204, which points to :
source $ORACLE_BASE/scripts/cshrc/10204/.cshrc
Meaning , I need to run in my k-shell script with the env settings parameters of the alias.
How to do it in k-shell?
Thanks in advance,
Nir (2 Replies)
I need to check if the parameters are correctly passed based on the Environment I am in.
For e.g when I am in dev the 1st paramter needs to be either A OR B OR C OR D
similarly when I am in qa the parameter needs to be either e or f
so i need to write a case staement or a if statement to... (1 Reply)
Okay, so I have a file containing line after line of three digit numbers. I need a script that does an action based on the last two numbers in this list.
So.... To get the last two numbers, I can have the script do
tail -2 filename.txt
But where I run into trouble is as follows. If... (6 Replies)
Hi everyone,
I wrote a script that is supposed to be run by cron on a daily basis. It works just fine if I run it manually, but due to a lack of environment variables (which are available during my user session but not when cron runs the script) it keeps failing to run successfully.
Here's the... (2 Replies)
Hi Team,
I have a to run a script based on a date present in a different file which updates everyday. Kindly help with the solution.
My current execution : ksh scriptname.sh 10152019. But here i want to enter this date from a file which gets updated daily.
My appraoch :
date file location:... (3 Replies)
Discussion started by: midhun3108
3 Replies
LEARN ABOUT MOJAVE
echo
ECHO(1) BSD General Commands Manual ECHO(1)NAME
echo -- write arguments to the standard output
SYNOPSIS
echo [-n] [string ...]
DESCRIPTION
The echo utility writes any specified operands, separated by single blank (' ') characters and followed by a newline ('
') character, to the
standard output.
The following option is available:
-n Do not print the trailing newline character. This may also be achieved by appending 'c' to the end of the string, as is done by iBCS2
compatible systems. Note that this option as well as the effect of 'c' are implementation-defined in IEEE Std 1003.1-2001
(``POSIX.1'') as amended by Cor. 1-2002. Applications aiming for maximum portability are strongly encouraged to use printf(1) to sup-
press the newline character.
Some shells may provide a builtin echo command which is similar or identical to this utility. Most notably, the builtin echo in sh(1) does
not accept the -n option. Consult the builtin(1) manual page.
EXIT STATUS
The echo utility exits 0 on success, and >0 if an error occurs.
SEE ALSO builtin(1), csh(1), printf(1), sh(1)STANDARDS
The echo utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'') as amended by Cor. 1-2002.
BSD April 12, 2003 BSD