05-27-2009
ok thanks but i want to know why it is work with this path /usr/xpg4/bin/awk
and doesn't work with /usr/bin/awk
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
zsh 4.3.4% cat file
ACFCFACCACARCSHFARCVJVASTVAJFTVAJVGHBAJ
zsh 4.3.4% cat file1
A
C
F
R
zsh 4.3.4% <file1 while read;do printf "%s=%d\n" "$REPLY" "${#$(<file)//}";done
A=9
C=7
F=4
R=2
That was the previous post.
But , can anybody can explain me in detail about this line
zsh... (2 Replies)
Discussion started by: dummy_needhelp
2 Replies
2. Shell Programming and Scripting
I did not understand what is ${0##/}
PGM=${0##/}
TMP=/tmp/${PGM}.$$
Please explain me. (2 Replies)
Discussion started by: gadege
2 Replies
3. Shell Programming and Scripting
could u please convert the below statement to shell script
----------
logdir=/smp/dyn/logfiles/cpm/pgm/pgIm
$logdir = $logdir ."/pgIm${toDate}*";
----
could u please explain the below clearly
grep -i adding $logdir | grep -iv equation | awk '{print \$NF}' | sort -u | sed -e... (1 Reply)
Discussion started by: mail2sant
1 Replies
4. AIX
this is the mksys b script....
can anyone explain .. what # and 1 in if condition
this is the first line of the script... it is not from middle of the script....
if
then
echo "Not enough parameters, need a client name for mksysb"
Usage="Usage: $0 <client name>"
... (2 Replies)
Discussion started by: honeym210
2 Replies
5. UNIX for Dummies Questions & Answers
if
then
echo "Syntax: $0 <sid> <COLD/HOT> <DEST>"
exit
fi
if --------------what does this mean???
echo "Syntax: $0 <sid> <COLD/HOT> <DEST>"---pls explain this as well (2 Replies)
Discussion started by: appsdba.nitin
2 Replies
6. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
I have a retake assignment to complete for my computer networks and OS class. This isn't really my area, had I known last year I could have swapped it for a different module I would have done so. I'm determined to get through it... (6 Replies)
Discussion started by: Squall Moogle
6 Replies
7. Shell Programming and Scripting
I'm trying to follow a script and I see it begins with this:
if ; then
if ; then
print "blah $0 blah blah "
exit
fi
fi
What does $# mean? I found out that $1 refers to the shell environment and the last argument that was entered or passed in the previous command. I couldn't find $#... (2 Replies)
Discussion started by: MaindotC
2 Replies
8. Shell Programming and Scripting
why the case 2 will happen ? , ' should stop the history substitution ,shouldn't it?
case 1
# echo "123"|sed '/123/!d'
123
case 2
# echo "123
> 456
> 1
> "|sed '/123/!d'
-bash: !d': event not found
case 3
# echo "123
> 456
> 12
> "|sed '/123/'\!d
123
# bash --version (1 Reply)
Discussion started by: justlooks
1 Replies
9. Shell Programming and Scripting
Can someone do me a favour and explain the following for me:
((r=$RANDOM%$n+1))
I know what $RANDOM does but what is % sign and what does it do with %$n+1? (2 Replies)
Discussion started by: bashily
2 Replies
10. UNIX for Dummies Questions & Answers
Hi friends! I'm learning UNIX and I have a small question. Working with Shell, i put the name of one executable (in c language) + one number and it says this:
$ gcc misterioso_4.c
$ ./misterioso_4 6
got: ,
I can not find an answer in the manual because I havent applied any variable.... (5 Replies)
Discussion started by: dakota
5 Replies
LEARN ABOUT OPENDARWIN
intro
INTRO(9) BSD Kernel Developer's Manual INTRO(9)
NAME
intro -- introduction to system kernel interfaces
DESCRIPTION
This section contains information about the interfaces and subroutines in the kernel.
PROTOTYPES ANSI-C AND ALL THAT
Yes please.
We would like all code to be fully prototyped.
If your code compiles cleanly with cc -Wall we would feel happy about it. It is important to understand that this isn't a question of just
shutting up cc, it is a question about avoiding the things it complains about. To put it bluntly, don't hide the problem by casting and
other obfuscating practices, solve the problem.
INDENTATION AND STYLE
Believe it or not, there actually exists a guide for indentation and style. It isn't generally applied though.
We would appreciate if people would pay attention to it, and at least not violate it blatantly.
We don't mind it too badly if you have your own style, but please make sure we can read it too.
Please take time to read style(9) for more information.
NAMING THINGS
Some general rules exist:
1. If a function is meant as a debugging aid in DDB, it should be enclosed in
#ifdef DDB
#endif /* DDB */
And the name of the procedure should start with the prefix DDB_ to clearly identify the procedure as a debugger routine.
SCOPE OF SYMBOLS
It is important to carefully consider the scope of symbols in the kernel. The default is to make everything static, unless some reason
requires the opposite.
There are several reasons for this policy, the main one is that the kernel is one monolithic name-space, and pollution is not a good idea
here either.
For device drivers and other modules that don't add new internal interfaces to the kernel, the entire source should be in one file if possi-
ble. That way all symbols can be made static.
If for some reason a module is split over multiple source files, then try to split the module along some major fault-line and consider using
the number of global symbols as your guide. The fewer the better.
SEE ALSO
style(9)
HISTORY
The intro section manual page appeared in FreeBSD 2.2.
BSD
December 13, 1995 BSD