bc error

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Print Error in Console and both Error & Output in Log file - UNIX

I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error. #! /bin/sh errExit () { errMsg=`cat...

2. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ...

3. Shell Programming and Scripting

What is this error log = hda: irq timeout: error=0x00 and how to solve?

what is this error log = hda: irq timeout: error=0x00 and how to solve? every day upon checking the logs i see this error. hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hda: irq timeout: error=0x00 hw_client: segfault at 0000000000000046 rip...

4. UNIX for Dummies Questions & Answers

> 5 ")syntax error: operand expected (error token is " error

im kinda new to shell scripting so i need some help i try to run this script and get the error code > 5 ")syntax error: operand expected (error token is " the code for the script is #!/bin/sh # # script to see if the given value is correct # # Define errors ER_AF=86 # Var is...

5. UNIX for Advanced & Expert Users

ssh error: Error reading response length from authentication socket

Hi - I am getting the error `Error reading response length from authentication socket' when I ssh from my cluster to another cluster, and then back to my cluster. It doesn't seem to affect anything, but it's just annoying that it always pops up and tends to confuse new users of the cluster. I...

6. Solaris

fssnap error :snapshot error: File system could not be write locked

Hi Guys. This is part of my filesystem structure : Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 47G 5.2G 42G 12% / /devices 0K 0K 0K 0% /devices ctfs 0K 0K 0K 0% ...

7. AIX

nim mksysb error :/usr/bin/savevg[33]: 1016,07: syntax error

-------------------------------------------------------------------------------- Hello, help me please. I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? : Command : failed stdout: yes stderr: no...

8. UNIX for Advanced & Expert Users

VSI-FAX error - Cannot login to server and Connecto error to host

I encounters a VSIFAX related error: vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument It started happening last night with a core dump. Then we can't start VSIFAX again. I am runing VSI-FAX 4.2 on AIX box

9. UNIX for Dummies Questions & Answers

awk Shell Script error : "Syntax Error : `Split' unexpected

hi there i write one awk script file in shell programing the code is related to dd/mm/yy to month, day year format but i get an error please can anybody help me out in this problem ?????? i give my code here including error awk ` # date-month -- convert mm/dd/yy to month day,...

10. UNIX for Dummies Questions & Answers

Error: Internal system error: Unable to initialize standard output file

Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message. Error: Internal system error: Unable to initialize standard output file I'm guessing more info might be needed, so let me know. Thanks

LEARN ABOUT FREEBSD

getopt

GETOPT(1)						    BSD General Commands Manual 						 GETOPT(1)

NAME

     getopt -- parse command options

SYNOPSIS

     args=`getopt optstring $*` ; errcode=$?; set -- $args

DESCRIPTION

     The getopt utility is used to break up options in command lines for easy parsing by shell procedures, and to check for legal options.
     Optstring is a string of recognized option letters (see getopt(3)); if a letter is followed by a colon, the option is expected to have an
     argument which may or may not be separated from it by white space.  The special option '--' is used to delimit the end of the options.  The
     getopt utility will place '--' in the arguments at the end of the options, or recognize it if used explicitly.  The shell arguments ($1 $2
     ...) are reset so that each option is preceded by a '-' and in its own shell argument; each option argument is also in its own shell argu-
     ment.

EXIT STATUS

     The getopt utility prints an error message on the standard error output and exits with status > 0 when it encounters an option letter not
     included in optstring.

EXAMPLES

     The following code fragment shows how one might process the arguments for a command that can take the options -a and -b, and the option -o,
     which requires an argument.

	   args=`getopt abo: $*`
	   # you should not use `getopt abo: "$@"` since that would parse
	   # the arguments differently from what the set command below does.
	   if [ $? -ne 0 ]; then
		   echo 'Usage: ...'
		   exit 2
	   fi
	   set -- $args
	   # You cannot use the set command with a backquoted getopt directly,
	   # since the exit code from getopt would be shadowed by those of set,
	   # which is zero by definition.
	   while true; do
		   case "$1" in
		   -a|-b)
			   echo "flag $1 set"; sflags="${1#-}$sflags"
			   shift
			   ;;
		   -o)
			   echo "oarg is '$2'"; oarg="$2"
			   shift; shift
			   ;;
		   --)
			   shift; break
			   ;;
		   esac
	   done
	   echo "single-char flags: '$sflags'"
	   echo "oarg is '$oarg'"

     This code will accept any of the following as equivalent:

	   cmd -aoarg file file
	   cmd -a -o arg file file
	   cmd -oarg -a file file
	   cmd -a -oarg -- file file

SEE ALSO

     getopts(1), sh(1), getopt(3)

HISTORY

     Written by Henry Spencer, working from a Bell Labs manual page.  Behavior believed identical to the Bell version.	Example changed in FreeBSD
     version 3.2 and 4.0.

BUGS

     Whatever getopt(3) has.

     Arguments containing white space or embedded shell metacharacters generally will not survive intact; this looks easy to fix but is not.  Peo-
     ple trying to fix getopt or the example in this manpage should check the history of this file in FreeBSD.

     The error message for an invalid option is identified as coming from getopt rather than from the shell procedure containing the invocation of
     getopt; this again is hard to fix.

     The precise best way to use the set command to set the arguments without disrupting the value(s) of shell options varies from one shell ver-
     sion to another.

     Each shellscript has to carry complex code to parse arguments halfway correctly (like the example presented here).  A better getopt-like tool
     would move much of the complexity into the tool and keep the client shell scripts simpler.

BSD
								 January 26, 2011							       BSD

Shell Programming and Scripting