[plug] unusual commands

[Ben New]

smclevie wrote:

> Hi
>
> I'm a little baffled with the following:
>
> $ export PATH=/opt/sun/bin:/usr/local/bin:/usr/local/sbin: 
> /usr/local/openssl/bin:/usr/sbin:/usr/bin:/usr/ccs/bin: 
> /usr/openwin/bin:/usr/dt/bin:/usr/platform/SUNW,Ultra-Enterprise/sbin: 
> /opt/SUNWexplo/bin
> $ export LD_LIBRARY_PATH=/usr/local/lib:/usr/local/ssl/lib: 
> /usr/local/openssl/lib:/usr/ccs/lib:/usr/openwin/lib: 
> /usr/local/lib/perl5/5.8.2/sun4-solaris/CORE
>
> I believe it is something related to an environment variable called 
> LD_LIBRARY_PATH.
>
> How does one know if it is 'set'? OR its setting??
>
> Thanks,
>
> Steve
>

RTFM! Which FM? "man 1 bash":

export [-fn] [name[=word]] ...
export -p
The supplied names are marked for automatic export to the envi-
ronment of subsequently executed commands. If the -f option is
given, the names refer to functions. If no names are given, or
if the -p option is supplied, a list of all names that are
exported in this shell is printed. The -n option causes the
export property to be removed from the named variables. export
returns an exit status of 0 unless an invalid option is encoun-
tered, one of the names is not a valid shell variable name, or
-f is supplied with a name that is not a function.


Try "set" to display all the environment variables. Also "echo 
$LD_LIBRARY_PATH" will show you the value of just that one variable.

Finally you have spaces and line breaks in your originally posted export 
commands. I expect this is due to posting via the list but if not, make 
it all one line with no spaces before or after the colons. Also I think 
you have a typo between "SUNW" and "Ultra-Enterprise".

P.S. The above assumes bash because no other was specified and it's what 
I'm using. Other shells may have different syntax.

-- 
Ben New
ben at leftclick.com.au

Leftclick Software Development
http://www.leftclick.com.au/