I am having problems with a part of my script. Basically it asks for the user to enter a new id number for them. The catches are:-
* It cannot already be existing (it will check a file)
* It has to be four characters
* It can only be numbers
* It cannot call back into the function
The first three parts are simple but not calling itself is causing me problems. I was thinking about using nested while loops and heres what i have got so far. (It feels like i have lost the plot!!)
Code:
read input
while [ $input < 9999 ]
do
while [ 'echo $input | wc -c' < 4 ]
do
while [ "$input" = 'grep $input file' ]
do
read input
done
read input
done
read input
done
hey , everyone. I have a few questions about pieces of code and was wondering if someone could tell me what exactly they did or if they are even valid.
bool1 && bool2 || bool3 <---in what order do these get processed?
if (! isdigit(c)) <---What does this do?
i = j % 3; <---what does this do?... (4 Replies)
Hi Folks,
I'm using bash script. I would like to check whether input is a number or not.(Only positive numbers).. if space or non numeric is entered, it should say "invalid input". pls help..
thanks in adv.
Br///
Vijay. (1 Reply)
Hello,
I am trying to write an expect script that will ssh into a large number of Cisco routers and add some commands via the cli. The script I wrote works great for one host however I have over 350 routers that this needs to be added to. The problem is I cannot get the script to read the file of... (1 Reply)
#include <iostream>
#include<stdio.h>
using namespace std;
class a
{
public:
int xx;
a()
{
cout << "in CONS a \n";
}
~a()
{
cout << "in DES a \n";
}
}; (1 Reply)
Experts,
In a script i get the following error:
The specified substitution is not valid for this command
Do you have any idea what is wrong with it?
TITLE="Code Checker" # Script Titel #
EXT="_UA99" # Eind van dirnaam #
FILE="job.dat" # Zoekbestandsnaam #
SEARCH="returncode 0" #... (1 Reply)
Could someone help me by midnight tonight!!!
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Insert a reference to the Bourne shell as the command... (0 Replies)
Ok so this is sort of a unix question. I am frequently logging into customers boxes and our product integrates with Active directory.
I deal with a great deal of people who have no business being admins but are and they don't know squat about their network or their DC's. So a recurring problem... (4 Replies)
Hi everyone,
I cant seem to figure this out for the life of me. Basically, I have two arrays..
sub init {
use Getopt::Long;
use Data::Dumper;
my @selections = ();
my @valid_options = ( "vaild1", "valid2" );
GetOptions( "input=s" =>... (2 Replies)
Hi,
echo "Enter file name of input file list along with absolute path : "
read inputFileList
if
then
for string in `cat inputFileList`
do
echo $string
done
else
echo " file does not exist"
fi
From the above code, if the user enters a invalid file... (1 Reply)
How to check the user input to be valid using shell script?
The valid input is in the format like as follows.
1. It can only have r,w,x or a hyphen and nothing else.
2. ensure the r, w, x are in the correct order.
for example: rwxr-xr-x is a valid format.
Thanks (5 Replies)
Discussion started by: hyeewang
5 Replies
LEARN ABOUT REDHAT
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)
09-22-2009
