03-28-2007
Quote:
Originally Posted by janmolby
Would anyone have details of pre-existing Unix shell scripting standards. I've been asked to prepare a document outlining standards when writing korn shell scripts & don't really know where to start. Thanks.
The Korn shell will run all scripts that conform to the POSIX standard for the shell. By writing scripts that conform to the standard, you will also be able to run them with other shells if that should ever be needed.
For more information see the standard at http://www.opengroup.org/onlinepubs/.../contents.html.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am looking for some coding standards for Unix Shell Scripting. Can anyone help me out in this?
Regards,
Himanshu (3 Replies)
Discussion started by: himanshu_s
3 Replies
2. UNIX IEEE Std 1003.1-2001 (POSIX.1)
Click HERE to learn about The Single UNIX Specification, Version 3
Or:
Here is another link to the UNIX IEEE Standard, an Open Group Technical Standard, Issue 7
Keywords
UNIX® is a registered trademark of The Open Group (0 Replies)
Discussion started by: Neo
0 Replies
3. Programming
I'm new to UNIX programming. I'm used to starting my program's versions at 1.0, but I look at all the UNIX programs out there and see things like 0.000.1 or 3.3.000 and I'm wondering what these things really mean. Do people just type anything they feel in there? Are things in pre-release... (6 Replies)
Discussion started by: hirni
6 Replies
4. Shell Programming and Scripting
please give the difference between AIX shell scripting and Unix shell scripting. (2 Replies)
Discussion started by: haroonec
2 Replies
5. Shell Programming and Scripting
Hi,
we are writing this fields dynamically retrieved from database and writing
into the file.
$bmpRec = $bmpRec.'|'.$cust_id; # sp4
$bmpRec = $bmpRec.'|'.$serv_id; # sp5
$bmpRec = $bmpRec.'|'.$site_id; # sp6
$bmpRec = $bmpRec.'|'.$loc_id; # sp7
... (4 Replies)
Discussion started by: Maruthi Kunnuru
4 Replies
6. Shell Programming and Scripting
Hi All,
Greetings!!
I am trying to write a script that will get me the syslog.log file output of last week...
That is ...my cron will run on Monday and will get me the syslog output of previous week , last monday-last sunday.
I tried using date formatting and tail..but did not succeed.... (4 Replies)
Discussion started by: premamadhuri
4 Replies
7. UNIX for Advanced & Expert Users
Hi Friends,
1. Bash Shell Scrpt to take backup at evening
2. I need a bash shell script for killing all processes. (5 Replies)
Discussion started by: vinayraj
5 Replies
8. Shell Programming and Scripting
Hi,
Can anyone point me to Secure coding standards for shell programming guides, links etc etc...
Thanks and regards,
Vamsi K Surampalli. (2 Replies)
Discussion started by: vamsisurampalli
2 Replies
9. UNIX for Dummies Questions & Answers
Hello Experts,
I have the following questions to be discussed here at this esteemed discussion forum.
I have two Excel sheets which contain Unix Commands llike creating directory the structure/ftp/Copy/Zip etc to basically create an environment. I need help in understanding some of... (1 Reply)
Discussion started by: faizsaadq
1 Replies
LEARN ABOUT DEBIAN
shell-quote
SHELL-QUOTE(1p) User Contributed Perl Documentation SHELL-QUOTE(1p)
NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS
--debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.8.4 2005-05-03 SHELL-QUOTE(1p)