On many systems, #!/usr/bin/env utility will work for many common cases.
On systems that support multiple programming environments (like Solaris systems that use $PATH to choose between SVID3, XGP3, XPG4, XPG5, XPG6, old BSD, etc. environments), something like #!/usr/bin/env cmd where cmd is sh, awk, grep, sed, or any other utility that has different versions depending on the environment chosen) might or might not give you what you want depending on how PATH is set by the user invoking your script.
Since I worked at Sun for more than twenty years, I almost never use #!/usr/bin/env. And, I would never use that in any script that I would expect to ever be run on a Solaris system to get access to any utility that uses internationalized regular expressions.
Note also that I frequently see people posting scripts that use:
or:
but on some systems (at least in the late 1980's and early 1990's when the first version of the POSIX utilities standard was being developed) everything following the #! is treated as the name of the interpreter to be invoked. On those systems (if any still exist):
will fail unless there is a utility named env<space>bash in /usr/bin. And, I'm pretty sure that there are still systems that will accept an interpreter name and one argument to it (as in the above invocation of bash), but won't accept more than one argument, such as in:
Hi,
Please clarify what is the difference between "env" and "set" command.
I guess set will display the system variables and user defined variables.
Thanks
Sweta (1 Reply)
Hi Friends,
Can any of you explain me about the below line of code?
mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`
Im not able to understand, what exactly it is doing :confused:
Any help would be useful for me.
Lokesha (4 Replies)
I need to take a string (stringA) check it for spaces and replace any spaces found with an equal (=) sign.
This is not working. There are spaces between each component:
$StringA | tr "" ""
The error returned is:
test: Specify a parameter with this command
Can you help? (3 Replies)
I am using ksh.. Whenever we write a shell script the first statement would be #! /bin/ksh. But instead of that I came to find "#@$-q large" in the first line and"#@$-s /usr/bin/ksh -x " in the second line. what does it mean?
Give your comments.....
Thanks
sabeer (4 Replies)
Hi,
could someone pls enlighten me on the difference between the "root" package and "usr" package?
Like in this example:
pkginfo -l SUNWGtku | grep -i desc
DESC: GTK - The GIMP Toolkit (Usr)
and
pkginfo -l SUNWGtkr | grep -i desc
DESC: GTK - The GIMP Toolkit (Root)... (6 Replies)
On a SunOS Solaris 5.5.1 workstation, the /usr/dt/bin/sdtdbcache –init command lasts more than 20 minutes. This command is executed by the /usr/dt/bin/Xsession script during an user connection.
Please refrain from using subjects like "HELP ME!..." to get more/faster attention and also please do... (1 Reply)
what if the difference between
#!/bin/sh
and
#!/bin/bash
I wrote a script with the second heading now when i change my heading to the first one ...the script is not executing well....im not getting the required output....any solution to this problem...or do i have to start the... (3 Replies)
The system don't boot.
on the screen appears following:
press enter to maintenance (or type CTRL-D to continue)...I checked with format command.
... the slices "0-root","1-swap","2-backup" exist.
...the slises "3-var","6-usr" -unassigned. :( (16 Replies)
I'm on Ubuntu 14.04 and I manually updated my coreutils so that "tee" is now on version 8.27
I was running a script using bash where there is some write to pipe error at some point causing the tee command to exit abruptly while the script continues to run. The newer version of tee seems to prevent... (2 Replies)