03-07-2008
position=1
#put the following in a loop
#cut -c stands for column
while [ $position -ge 8 ]
do
echo `cut -c$position`
position=`expr $position + 1`
done
10 More Discussions You Might Find Interesting
1. AIX
I've just started to explore NIM and I'm looking for additional information on how to set it up and configure it. I've read through the "NIM A-Z" and have many unanswered questions.
One question is how can I have the NIM server pull a mksysb of the clients and can I schedule this to happen... (1 Reply)
Discussion started by: scottsl
1 Replies
2. What is on Your Mind?
Hi,
I am a newbie to Unix, I was introduced to UNIX 8 months back during my Training, I was attracted to Unix as they give complete freedom. I would like to ask how can a OS Admin can go into development field of Unix. Currently I am working in a MNC in Backup- Storage Admin Domain I am... (1 Reply)
Discussion started by: sufi_431
1 Replies
3. UNIX for Advanced & Expert Users
Hi all,
I am trying to get the exception count daily from a log file which is more than 1 GB in size.
I am using loops which get the count of the exception and transaction. But i need to take this exception count for a time frame from 5.00 am to 5:00 pm.
I Think I can use to exact the... (4 Replies)
Discussion started by: senthilkumar_ak
4 Replies
4. HP-UX
Hello,
We've recently had a multiple hardrive failure in our legacy HP9000. Now the drives are repaired and the filesystems are recreated, I went to restore the last of the database tables from our dds3 backup, but cannot. Here's what's going on: BTW, I'm an absolute novice w/ HP-UX
The... (5 Replies)
Discussion started by: jastuart
5 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I am new with updates in RHEL especially servers. The question is:
1. Do I need to register to RHEL in order for me to use the up2date?
2. For updates in RHEL need to use up2date, but what is the thing that I need to do before the patches? I mean what should I backup in case my patches... (0 Replies)
Discussion started by: flekzout
0 Replies
6. Shell Programming and Scripting
Hi ,
I have a txt file with contents like:
1234
2345
3456
7891
I need to write a script which takes input file as txt file..run a sql query for that number and place the output of query in another file..
select * from bus_event where acct_nbr='1234'( from input txt file)
the query... (20 Replies)
Discussion started by: Rajesh Putnala
20 Replies
7. AIX
I need some guidance on the differences in observations, not sure how significantly different are they.
Also, It would be nice to hear on the values and what the obvious tuning for performance missing.
Observation 1
ending vmstat -v 3948544 memory pages
ending vmstat -v ... (1 Reply)
Discussion started by: Snipper
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am trying to debug some KSH script and it has the nawk portion below. I just want to confirm whether I understand what it does correctly.
Example usage of the nawk line is run as below:
nawk '/^#/ {next}
$1~/^'testp.cfg'$|^'testp.cfg'\.testdb\.com\.ph$/ {
c=0
while... (1 Reply)
Discussion started by: newbie_01
1 Replies
9. Shell Programming and Scripting
Hey All,
I am newbie on scripting and need some guidance from all the experts here.
I am working on one project where I will check the status/health of around ten (10) solaris 10 servers.
I have one central server from where I have already setup the passwordless SFTP and setup the cron... (1 Reply)
Discussion started by: supercops
1 Replies
10. AIX
Hi There,
I am new to AIX. I am eager to learn the AIX System administration or if there is any other prerequisite before this. Please can anyone help me or guide how to start with AIX, what all courses and certifications do I need to do. I have basic knowledge of UNIX.
Please guide as I am... (3 Replies)
Discussion started by: rahulat302
3 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)