Thanks Perderabo. But what if i dont give this statement called magic numbers in my shell...

Anything wrong in it.. it almost looks like a coding standard for the script that we write...

Thanks,
Nisha

If you leave it out, then the shell will fail when it tries to exec() it. What happens next depends on which shell you are using as your login shell. Most shells will assume that the script is written in their own language. So if you are using bash as your login shell and try to run a korn shell script that didn't have the #! /usr/bin/ksh, then bash will try to run it as a bash script. bash and ksh are somewhat compatible and this might work. On the other hand, it might fail.

Suppose you use ksh as your login shell and you are running korn shell scripts without that first line. Things seem ok. Then you decide to try bash as your login shell. Suddenly things break.

And things will be especially grim for anyone who uses csh/tcsh as their login shell and runs scripts without that first line. These shells inspect the script to try and guess whether they or the old bourne shell should run it. The test they employ is so bad that it can be beaten by a random number generator. And no one still uses the old bourne shell anyway.

And yes, it is sort of a standard. Most kernels know about it. But I don't believe that is an official posix standard.

Thank you Perderabo..

That clears my doubts...

Thanks,
Nisha

Also, from the USENET Unix FAQS, see Why do some scripts start with #! ... ?
And see this page and scroll down to the RATIONALE section near the end for info about a trailing hyphen on this line.