Sponsored Content
Top Forums Shell Programming and Scripting syntax of if condition in ksh is wrong Post 302550456 by fpmurphy on Thursday 25th of August 2011 11:22:58 PM
Old 08-26-2011
No need to do
Code:
if [[ $(( version > 2.1 )) == 1 ]]

in ksh93

This works just as well and is a cleaner syntax
Code:
if (( version > 2.1 ))
then
     echo "version is correct"
else
     echo "version is wrong"
fi

 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

What was wrong ??? ksh

I wrote this code and did not know what did I do wrong ?? ## get the first line of this file AFIRST=$(head -1 rss-cs-3423a-20051211-060001.dat) #CJKA|2005-12-10 08.01.30.000000|1111111111|ECI|1112221111|1113331111|1114441111 <--- this is a answer ## Third line of stat file BTHREE=$(cat... (11 Replies)
Discussion started by: sabercats
11 Replies

2. Shell Programming and Scripting

. $startApache wrong syntax?

Hi All, why doesn't this code start apache at boot? Cheers. coolboarderguy... startApache=/usr/local/apache2/bin/apachectl start if ; then . $startApache fi (5 Replies)
Discussion started by: coolboarderguy
5 Replies

3. Shell Programming and Scripting

Whats wrong with the syntax

Whats wrong with below logic or syntax???? (4 Replies)
Discussion started by: dsravan
4 Replies

4. Shell Programming and Scripting

Whats wrong with this IF condition?

I have four variables, dumpdata, defndata, compare1 and compare2 I want an IF statement condition which returns true when either dumpdata=defndata or (dumpdata<=compare1 and dumpdata>=compare2). But this is not working for me.. if (4 Replies)
Discussion started by: indianjassi
4 Replies

5. Shell Programming and Scripting

Help with IF Condition Syntax

Hi. I expect the following unix script command to return 8: ls -ltr dropez* | grep -c dropez I can't seem to find the correct syntax (borne shell), can anyone help be to write an IF condition something like this: IF (ls -ltr dropez* | grep -c dropez) = 8 THEN ...do stuff ELSE ...do... (4 Replies)
Discussion started by: buechler66
4 Replies

6. Shell Programming and Scripting

Help with ksh using OR condition

I'm having an issue using OR condition, the script seems to work just fine but gives an error message while executing as can be seen in BOLD RED below: Code: #cat test.sh #!/bin/ksh set -x if || > /dev/null 2>&1;then echo "Fibre adapter found" else echo "No fibre... (10 Replies)
Discussion started by: mbak
10 Replies

7. Shell Programming and Scripting

What's wrong with this condition

if Please indicate the problem with this code Thanks in advance :) (4 Replies)
Discussion started by: ezee
4 Replies

8. Shell Programming and Scripting

What's wrong with this condition

if && ] then + : test: ] missing Thanks in advance :) (8 Replies)
Discussion started by: ezee
8 Replies

9. UNIX for Dummies Questions & Answers

[Solved] ksh script - can't figure out what's wrong

Hi! (I guess this could of gone into the scripting forum, but Unix for Dummies seemed more appropriate. Please note that I am not in school, so Homework doesn't seem appropriate either. You guys can let me know if you think otherwise.) I am following an exercise in a book on ksh scripting which... (2 Replies)
Discussion started by: sudon't
2 Replies

10. Shell Programming and Scripting

If condition giving syntax error. Need help.

Hi, I have an if condition on executing it is giving syntax error as below: -------------------------------------------------------------------------------------- line 61: syntax error in conditional expression ./play_test.sh: line 61: syntax error near `]' ./play_test.sh: line 61: ` if... (2 Replies)
Discussion started by: ramki067
2 Replies
print(1)							   User Commands							  print(1)

NAME
print - shell built-in function to output characters to the screen or window SYNOPSIS
ksh print [-Rnprsu [n]] [arg]... ksh93 print [-Renprs] [-f format] [-u fd] [string...] DESCRIPTION
ksh The shell output mechanism. When no options are specified, or when an option followed by ' a - is specified, or when just - is specified, the arguments are printed on standard output as described by echo(1). ksh93 By default, print writes each string operand to standard output and appends a NEWLINE character. Unless, the -r, -R, or -f option is speciifed, each character in each string operand is processed specially as follows: a Alert character.  Backspace character. c Terminate output without appending NEWLINE. The remaining string operands are ignored. E Escape character (ASCII octal 033). f FORM FEED character. NEWLINE character. Tab character. v Vertical tab character. \ Backslash character. x The 8-bit character whose ASCII code is the 1-, 2-, or 3-digit octal number x. OPTIONS
ksh The following options are supported by ksh: -n Suppresses new-line from being added to the output. -r-R Raw mode. Ignore the escape conventions of echo. The -R option prints all subsequent arguments and options other than -n. -p Cause the arguments to be written onto the pipe of the process spawned with |& instead of standard output. -s Cause the arguments to be written onto the history file instead of standard output. -u [ n ] Specify a one digit file descriptor unit number n on which the output is placed. The default is 1. ksh93 The following options are supported by ksh93: -e Unless -f is specified, process sequences in each string operand as described above. This is the default behavior. If both -e and -r are specified, the last one specified is the one that is used. -f format Write the string arguments using the format string format and do not append a NEWLINE. See printf(1) for details on how to specify format. When the -f option is specified and there are more string operands than format specifiers, the format string is reprocessed from the beginning. If there are fewer string operands than format specifiers, then outputting ends at the first unneeded for- mat specifier. -n Do not append a NEWLINE character to the output. -p Write to the current co-process instead of standard output. -r Do not process sequences in each string operand as described above. -R If both -e and -r are specified, the last one specified is the one that is used. -s Write the output as an entry in the shell history file instead of standard output. -u fd Write to file descriptor number fd instead of standard output. The default value is 1. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 Output file is not open for writing. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
echo(1), ksh(1), ksh93(1), printf(1), attributes(5) SunOS 5.11 27 Mar 2008 print(1)
All times are GMT -4. The time now is 11:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy