I'm new to scripting and I need help with a bourn shell script. What i'm trying to do is a test condition where "if the time is within 2 hours, it's true" and so on.
The time is in the following format
DATE=`/bin/date +"%Y%m%d%H%S"`
for example, 20060907152000.
So, what the script first... (9 Replies)
Hi ,
I have a doubt on condition test ( ] ). Pls refer blow program.
#!/bin/ksh
TEMP=
if ;then
echo $TEMP
else
print 'invalid option'
fi
Above script's TEMP variable has no value so it gives "invalid option" as output. But I got an error before priting the string .
Result :
... (2 Replies)
Hi there,
When I try to do a condition on test:
$ str1=abcd
$ test $str1
$ echo $?
0
Is there anyway to display the answer to be 'TRUE' or 'YES'? rather than 0?
If so, how can I do it without using awk or sed. (2 Replies)
Hello,
what is the better and correct way to perform a comparison:
I have been using the following with no problems:
if ]
then ....
fi
I have seen this also used :
if
then ....
fi
When I try :
if
then ....
fi
I get an error like .... the test condition expects a... (4 Replies)
Hi there,
I tried to search for this almost everywhere, but didnt get any proper information on it.
What is the difference between
]
Some of the code works when I have only single condition i.e.
] && $dothis1 || $dothis2
But if i try to include another testcondition to the... (1 Reply)
I have a much larger script that takes an input file of hosts and determines if we support them and checks to ensure the FQDN coincides with our DNS. For instance, the hostname may return a different FQDN when passed to the "host" command, so I keep the value of the output of the "host" command... (4 Replies)
I want to locate directories that are upper, lower or have both upper and lower cases.
What I have is:
find /tmp/$var2 -type d' " ); && echo "host case is incorrect" || echo "host case is correct"
This actually is part of a larger script and it does work but the problem is that it... (3 Replies)
Without grep, I'd like to make a test condition so that any a word that does not have the successive letters car in it will be echoed. for example, bluecar will contain "car" so it will show up as a no
var=bluecar
$ echo $var|if ]; then echo "yes";fi
yes
this variable contains "car" so I... (5 Replies)
i have to test a condition for n times and if its value is greater than one each time for continuous 5 iterations it will take action
My Approach
run the same command 5 times in for loop and divert the output to a file and then read the values from file and use if else if and take action
... (1 Reply)
Discussion started by: abhaydas
1 Replies
LEARN ABOUT LINUX
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)