04-17-2009
Not an actual shell, it's a set of features a shell has to implement to be considered POSIX-compliant, mostly from the ancient Bourne shell. I believe BASH and KSH are both posix compliant, but they add a lot more features as well.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Let's say I have
alias good_op=`]`
in a Korn shell script. How can I write that in a non-interactive bash shell? (5 Replies)
Discussion started by: jpprial
5 Replies
2. Shell Programming and Scripting
Hi, how do I write this condition in korn shell:
file="*.html"
if
then
echo "$file"
fi
I am trying to find all html files from a input text file that were created today and ftp them to a different server. please help. (1 Reply)
Discussion started by: sajjad02
1 Replies
3. Shell Programming and Scripting
Hi I am new to shell programming. I need help to write a script to monitor a process on Sun OS. If the process fails then call a oracle procedure.
i check the process if running by typing
ps -ef | grep ESP | grep -v grep
root 29002 1 0 Mar 18 ? 7:20... (4 Replies)
Discussion started by: gpanesar
4 Replies
4. UNIX for Dummies Questions & Answers
Everything else seems to be working, but this isn't. Is it the "cat..." that is wrong of the condition? Thanks.
cat tc_result.txt | while read LINE
do
if
then
let "files_run += 1";
echo "inside the if loop"
# save current filetype
case $LINE... (5 Replies)
Discussion started by: brdholman
5 Replies
5. Shell Programming and Scripting
I am using korn shell but I want to have my prompt to represnent that of my C shell because I like it better. Is there anyway to do this? (1 Reply)
Discussion started by: vthokiefan
1 Replies
6. Shell Programming and Scripting
Hi,
Im trying to write this script but im stuck on it, basicaly what i want to do is to write a code to verify a log file ( apache log file for example ) and for each new line with specific data , then, output this new line for another file:
full ex:
output of the server.log is (... (4 Replies)
Discussion started by: Thales.Claro
4 Replies
7. Shell Programming and Scripting
Hi guys,
I am new to unix scripting.
I have a folder rx and it has subfolders rx1,rx2 and rx3
each subfolder has 4 directories each load,land,arch and extr
I have the below tar and rm commands using wich we should write a shell script
rx1--
tar -cf... (2 Replies)
Discussion started by: Kornscript
2 Replies
8. Shell Programming and Scripting
I am relatively new to shell scripting. I have a script I wrote that works fine in korn shell.
I need to make it work in bash on a different server.
There are a couple valid korn shell commands I am having difficulty finding the bash equivalents for.
At one point the scripts prompts the... (5 Replies)
Discussion started by: inakajin
5 Replies
9. Shell Programming and Scripting
I am new to korn shell and slowly learning. Is there a way to have a parent script prompt for input and then execute a child script and return the output then move forward and ask for more input and then execute the next child script? I think the answer is no but thought i would ask. (2 Replies)
Discussion started by: cptkirkh
2 Replies
10. Shell Programming and Scripting
Migrating Unix batch jobs (Korn Shell) running in HP-UX server to Linux environment.
Hi All
Please help me to understand the easiest way to migrate Kernel Shell scripts to Linux Bash. Also let me know
1. Any automated scripts or tools available for this.
2. Challenges and issues... (5 Replies)
Discussion started by: cpremesh
5 Replies
LEARN ABOUT XFREE86
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)