04-26-2007
what's the largest shell script you've ever written?
I've just written a test harness using ksh.
One of scripts weighed in at 1206 lines.
I came across Eric Raymonds 'Art of Unix programming' on line and he advises against excessively large scripts.
I am very interested to hear people's opinions on this and any experiences they have had.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
There are 2 shell script files sh1 and sh2.
sh2 contains records such as 01 02 03 on different lines.
In sh1, I would like to read each record of sh2 till end of file, concatenate them with a comma(,) and store in a variable.
Can somebody please help me with the sh1 script?
Thanks in... (2 Replies)
Discussion started by: shsandeep
2 Replies
2. Shell Programming and Scripting
There are 2 shell script files sh1 and sh2.
sh2 contains records such as 01 02 03 on different lines.
In sh1, I would like to read each record of sh2 till end of file, concatenate them with a comma(,) and store in a variable.
Can somebody please help me with the sh1 script?
Thanks in... (6 Replies)
Discussion started by: shsandeep
6 Replies
3. UNIX for Dummies Questions & Answers
Is HP UNIX and Korn different flavours of unix?
can a korn shell script be written on HP Unix? (4 Replies)
Discussion started by: soujanya_srk
4 Replies
4. Shell Programming and Scripting
I have two text files like this:
file1.txt:
133 10
133 22
133 13
133 56
133 78
133 98
file2.txt:
158 38
158 67
158 94
158 17
158 23
I'm basically trying to have awk check the second largest value of the second column of each text file, and cat it to its own text file. There... (13 Replies)
Discussion started by: theawknewbie
13 Replies
5. UNIX for Advanced & Expert Users
Hi
I do a very simple monitoring of our OpenLDAP (runs in cronjob and generate alerts if unsuccessfull)
$ ldapsearch -h hostname.domain -D "cn=monitor_user,ou=People,dc=organisation" -w "password" -b "dc=organisation" -x "(&(cn=monitor_user)(ou=People))" dn | grep -v version
dn:... (4 Replies)
Discussion started by: slashdotweenie
4 Replies
6. Programming
Hello,
I am new on PHP scripting .I have shell scripts which I an running currently from linux server but now I want to make a web portal from where I will run all my scripts but the problem is all my scripts ask for parameters so I am getting confused how could I run my shell script from web... (2 Replies)
Discussion started by: anuragpgtgerman
2 Replies
7. Shell Programming and Scripting
In my quest to solve a bigger problem (See my previous post called "Create SQL DML insert statements from file using AWK or similar" - sorry, not allowed to post urls until I have > 5 posts) I'm trying to get my head round awk, but have some problem figuring out why the following script does work... (2 Replies)
Discussion started by: Yagi Uda
2 Replies
8. Shell Programming and Scripting
I have to hit a very large database to pull fields of information.
I have a script that runs multiple instance of the same query against the data base and writes contents to a file.
The script terminates before the file is completely written to confirmed by
ps -ef | grep <script name>... (3 Replies)
Discussion started by: popeye
3 Replies
9. Shell Programming and Scripting
The POSIX shell standard grammar rules are at
Shell Command Language
I am trying to understand Rule 7 and I don't. I think there may be some mistakes there. I am not complaining about the standard; rather, I am concerned that my perception is wrong, and I don't understand something important.... (3 Replies)
Discussion started by: Mark_Galeck
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)