@metal005 Your script as posted contains syntax and logic errors. Needs to be an OR test and all variables should be quoted because we need to look at empty variables.
I declared a variable x that gets the count(*) from a table. The table name is also defined as a variable.
What's wrong with this statment :
X=” select count(*) from ${table_name}“
then
y = `${X}${table_name}'
echo ${y}
It throws an error saying count not found.
Please... (1 Reply)
i have variables with different values as below in KSH
AU_Holiday=1
SG_Holiday=0
KR_Holiday=1
JP_Holiday=0
$country_cd is the second variable which be one of 'AU' 'SG' 'KR' 'JP' which comes in a for loop.
form that i need to derive the variable like first one and check whether it is equal... (3 Replies)
Hi all,
How to print variable value which i have assigned inside for loop
because that variable scope is local, but i want to use that variable outside for loop.
Awaiting your great help
Thanks,
Susil (1 Reply)
Dear Unix experts
I want to define a variable which contains dynmic and static part, daynamic part is the first field.
Sample of data
dddd aaaa sssss 12345
ssss 2323 234234 4242
dddd 3223 34234 54353
ssss 24234 3434 42342
dddd rwrw 423423 werwer
nawk 'BEGIN {FS=" "}{... (4 Replies)
Anyone please say what is the difference between $var and ${var} in perl
Sometimes $var used and sometimes ${var} used in same program.
Thanks in Advance,
Prabhu
---------- Post updated at 09:34 AM ---------- Previous update was at 05:59 AM ----------
Any one please clarify (1 Reply)
Dear Unix experts
Moved from "Shell Programming and Scripting "
I want to define a variable which contains dynmic and static part, daynamic part is the first field.
Sample of data
dddd aaaa sssss 12345
ssss 2323 234234 4242
dddd 3223 34234 54353
ssss 24234 3434 42342
dddd rwrw 423423... (2 Replies)
Hello,
Why is this not working in a script?
files="test.fsa"
echo $files
for file in $files
do
if
then
echo "$file does not exist."
fi
run a command
done
I get an error saying (3 Replies)
Discussion started by: verse123
3 Replies
LEARN ABOUT OPENDARWIN
script
SCRIPT(1) BSD General Commands Manual SCRIPT(1)NAME
script -- make typescript of terminal session
SYNOPSIS
script [-a] [-k] [-q] [-t time] [file [command ...]]
DESCRIPTION
The script utility makes a typescript of everything printed on your terminal. It is useful for students who need a hardcopy record of an
interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).
If the argument file is given, script saves all dialogue in file. If no file name is given, the typescript is saved in the file typescript.
If the argument command ... is given, script will run the specified command with an optional argument vector instead of an interactive shell.
Options:
-a Append the output to file or typescript, retaining the prior contents.
-k Log keys sent to program as well as output.
-q Run in quiet mode, omit the start and stop status messages.
-t time Specify time interval between flushing script output file. A value of 0 causes script to flush for every character I/O event. The
default interval is 30 seconds.
The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-d (if
ignoreeof is not set) for the C-shell, csh(1)).
Certain interactive commands, such as vi(1), create garbage in the typescript file. The script utility works best with commands that do not
manipulate the screen. The results are meant to emulate a hardcopy terminal, not an addressable one.
ENVIRONMENT
The following environment variable is utilized by script:
SHELL If the variable SHELL exists, the shell forked by script will be that shell. If SHELL is not set, the Bourne shell is assumed. (Most
shells set this variable automatically).
SEE ALSO csh(1) (for the history mechanism).
HISTORY
The script command appeared in 3.0BSD.
BUGS
The script utility places everything in the log file, including linefeeds and backspaces. This is not what the naive user expects.
It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.
When running in -k mode, echo cancelling is far from ideal. The slave terminal mode is checked for ECHO mode to check when to avoid manual
echo logging. This does not work when in a raw mode where the program being run is doing manual echo.
BSD June 6, 1993 BSD