Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: bc giving error: (standard_in) 2: parse error
Top Forums Shell Programming and Scripting bc giving error: (standard_in) 2: parse error Post 302442291 by manishma71 on Wednesday 4th of August 2010 01:35:53 AM
Old 08-04-2010
pravin and agn - looks like what you guys said is not helping

#################### CODE ####################
Code:
#!/bin/sh

a="1.23"
b="2.45"

if [ $a > $b ]; then 
    echo "string compare: greater : $a > $b"
else
    echo "string compare: smaller : $a < $b"    
fi

if [ $a -ge $b ]; then 
    echo "int compare: greater : $a > $b"
else
    echo "int compare: smaller : $a < $b"   
fi

if [ $( echo "$a > $b" | bc ) -eq 1 ]; then 
    echo "using bc: greater : $a > $b"
else
    echo "using bc: smaller : $a < $b"
fi

exit 0

#########################################

and output is

Code:
$ ./test.sh
string compare: greater : 1.23 > 2.45
./test.sh: line 12: [: 1.23: integer expression expected
int compare: smaller : 1.23 < 2.45
using bc: smaller : 1.23 < 2.45

the first greater is wrong and second (-le/-ge) is giving error

---------- Post updated at 11:05 AM ---------- Previous update was at 11:05 AM ----------

i want to know the reason for this error:
Code:
(standard_in) 2: parse error
(standard_in) 1: parse error

shell error will go if "bc" works fine.
Last edited by pludi; 08-04-2010 at 03:57 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

script giving error

Hi All, i have an small issue... echo " " eval x=$@ export x=`echo $x` echo $x ssh user@ipadrss; cd /mbbv/home/; cd /mbbv/home/orange/orange/ echo pwd bash samplescript.sh $x above is my script which will triger from server A and will connect to server B for some... (2 Replies)
Discussion started by: Shahul
2 Replies

2. Linux

acroread command giving error

Hi, When I run the command acroread it is giving error ERROR: Cannot find installation directory. When I look at /usr/local/Adobe/Acrobat7.0/bin/ an exicutable file named acroread is there. When i run ./acroread from that directory it is working . What can i do so that I can give... (3 Replies)
Discussion started by: iamjayanth
3 Replies

3. UNIX and Linux Applications

apt-get install giving error

Hello when i am giving a command apt-get install I am getting error as below: " apt-get: error while loading shared libraries: libapt-pkg-libc6.3-6.so.3.11: cannot open shared object file: No such file or directory " can u suggest what to do. https://www.unix.com/images/misc/progress.gif... (1 Reply)
Discussion started by: pradeepreddy
1 Replies

4. BSD

Xarchiver giving error messages

I have FreeBSD installed with Xarchiver and when extracting files through the file manager ("Extract here..." option) the following error pops up: tar: unrecognized option `--overwrite' Perhaps this is a known error and is there a way to solve it? (10 Replies)
Discussion started by: figaro
10 Replies

5. Shell Programming and Scripting

(standard_in) 1: parse error

Hi all, Could someone please to tell me when do we exactly get the below error and how to get rid of it. I am unable to trace the error. (standard_in) 1: parse error Thanks in advance !! (4 Replies)
Discussion started by: sparks
4 Replies

6. AIX

multipath giving error

Hi, # lspath Missing hdisk0 fscsi0 Missing hdisk1 fscsi0 Missing hdisk2 fscsi0 Missing hdisk3 fscsi0 Missing hdisk4 fscsi0 Missing hdisk5 fscsi0 Missing hdisk6 fscsi0 Missing hdisk7 fscsi0 Missing hdisk8 fscsi0 Missing hdisk9 fscsi0 Missing hdisk10 fscsi0 Missing hdisk11... (2 Replies)
Discussion started by: JATA01
2 Replies

7. Shell Programming and Scripting

(standard_in) 1: parse error

Hi, I am trying to make a script that tries to compare two values and print if one is greater than another. It seems to return a (standard_in) 1: parse error at times. #!/bin/sh a= awk '{print $1}' file1.txt b= awk '{print $1}' file2.txt c= awk '{print $1}' file3.txt x= awk '{print... (5 Replies)
Discussion started by: jamie_123
5 Replies

8. 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

9. Shell Programming and Scripting

Standard_in error

# echo '6.5 < 2.7 ' |bc 0 # echo '4.8.5 > 4.8.4' |bc (standard_in) 1: syntax error (standard_in) 1: syntax error ---------------------------------------------------------- FILESET_A_VER_CHK2=4.8.5 FILESET_R_NAME_CHK2=4.8.5 if ] ; then ## echo "Fileset is higher " ... (2 Replies)
Discussion started by: Mathew_paul
2 Replies

10. Shell Programming and Scripting

(standard_in)1:syntax error using bc with Cron

I created a shell script to record server temperature. When I manually run script it works fine with no error message. But when I create a cron job, my script fails with error message (standard_in)1:syntax error. I figured out the bc utility is causing the error message. Below is my script. ... (7 Replies)
Discussion started by: SysAdminRialto
7 Replies

LEARN ABOUT NETBSD

checkbashisms

CHECKBASHISMS(1)					      General Commands Manual						  CHECKBASHISMS(1)

NAME

       checkbashisms - check for bashisms in /bin/sh scripts

SYNOPSIS

       checkbashisms script ...
       checkbashisms --help|--version

DESCRIPTION

       checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
       of bashisms.  It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.

       Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported  by  POSIX";
       this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.

       In  cases  where  POSIX	and  Debian  Policy  disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
       options for stricter checking.

OPTIONS

       --help, -h
	      Show a summary of options.

       --newline, -n
	      Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)

       --posix, -p
	      Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).

       --force, -f
	      Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
	      to be a shell wrapper).

       --extra, -x
	      Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
	      tive which may be ignored.  For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.

       --version, -v
	      Show version and copyright information.

EXIT VALUES

       The exit value will be 0 if no possible bashisms or other problems were detected.  Otherwise it will be the sum of the following error val-
       ues:

       1      A possible bashism was detected.

       2      A file was skipped for some reason, for example, because it was unreadable or not found.	The warning message will give details.

SEE ALSO

       lintian(1).

AUTHOR

       checkbashisms  was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
       Julian Gilbey <jdg@debian.org>.

DEBIAN
								 Debian Utilities						  CHECKBASHISMS(1)
All times are GMT -4. The time now is 05:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy