01-12-2017
Unfortunately, the code I suggested in post #15 only works if all zeros in the string are leading zeros.
Fortunately, RudiC posted the fix that does what I was trying to do in post #18.
Thanks RudiC!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a script which takes a value from a file and performs calculations on it. Trouble is that this value is a float not an integer and it errors at the decimal point!
eg. 94.62
I would like to be able to detect the length of the float (in this above case, 5 characters), and simply do a... (2 Replies)
Discussion started by: danhodges99
2 Replies
2. Shell Programming and Scripting
Hi ...
I am trying to calculate the time needed for a command to execute..
but the resulting value is getting as string..
so i am not able to use "expr " command..
please help me to convert the value to integer so that i can proceed with my script..
Regards
esham (1 Reply)
Discussion started by: esham
1 Replies
3. Shell Programming and Scripting
Hi
i have a string value in a variable STR
eg. STR="ABSDSCSFS"
How can be convert it to LOWERCASE in the script?
Thanks (5 Replies)
Discussion started by: skyineyes
5 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am passing a variable to a unix function.
However when I try to assign the value to another variable like
typeset -i I_CACHE_VAL=$2
Is this because of String to Integer conversion?
I get an error.
Please help me with thsi.
Thanks (2 Replies)
Discussion started by: neeto
2 Replies
5. Shell Programming and Scripting
Hi everyone,
I would like to know how to convert an integer to a string. for instance if i=1 i would like to creat a variable called constant1. i want to do this in a for loop so for each value of i, i create a new variable such as constant2, constant3,... and so on.
for i in 1 2 3
do ... (1 Reply)
Discussion started by: ROOZ
1 Replies
6. UNIX for Advanced & Expert Users
I'm attempting to read a file that is composed of complex 32-bit floating point values on Solaris 10 that came from a 64-bit Red Hat computer.
When I first tried reading the file, it looked like there was a byte-swapping problem and after running the od command on the file Solaris and Red Hat... (2 Replies)
Discussion started by: GoDonkeys
2 Replies
7. Shell Programming and Scripting
here is a code
column_name="vivek"
column_name2="ViVeK"
column_name=$(echo $column_name | awk '{print tolower($0)}')
column_name2=$(echo $column_name2 | awk '{print tolower($0)}')
echo "column name 1 lower: $column_name"
echo "column name... (6 Replies)
Discussion started by: vivek d r
6 Replies
8. Shell Programming and Scripting
okay so i run an openssl command to get the date of an expired script. Doing so gives me this:
enddate=Jun 26 23:59:59 2012 GMT
Then i cut everything out and just leave the month which is "Jun"
Now the next part of my script is to tell the user if the the certificate is expired or not... (6 Replies)
Discussion started by: shade917
6 Replies
9. Shell Programming and Scripting
Dear community,
i got a problem to get "date +%j" as the right value.
Today is the 10th day of the year.
#./script.sh 2
#!/bin/bash/
Var1=$(date +%j)
Var2=$1
let result=$Var1+$Var2
echo $Var1 plus $Var2 equals $result
The output of the script is:
010 plus 2 equals 10... (9 Replies)
Discussion started by: OskarHF
9 Replies
10. Shell Programming and Scripting
I have a function that is supposed to check for user processes and wait for 0 count before exiting the function. I am sure I have more than one issue in my code, but the stumbling block right now is that I am trying to convert the value of my variable from a string to integer.
process_count... (10 Replies)
Discussion started by: MIA651
10 Replies
LEARN ABOUT HPUX
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)