if [ $COMPILER = "sun" ]; then
if [[ -f /sunstudio12/bin/sunf90 ]]; then
export IMDI_COMPILER=/sunstudio12/bin/sunf90
else
echo "Please specify location!"
exit
fi
if [[ -z "$SZIP_ROOT" ]]; then
SZIP_ROOT=/szip-2.1
fi
elif [ $COMPILER = "intel" ]; then
i have this program in bash shell:
#!/bin/bash
array=(20 20 20 20 20)
i=0
j=0
awk '/%/ {print $3}' try.txt|
while (read s)
arr=$s
i=`expr $i + 1`
echo "$i"
end
how can i convert this into c shell? (1 Reply)
Discussion started by: npatwardhan
1 Replies
4. Post Here to Contact Site Administrators and Moderators
Where can I download the VTC - Unix Shell Scripting Advanced complete video.
I don't know in which thread I should post this question.Plz help me out, or just tell me the link in the reply to this post.
Thanks in advance. (0 Replies)
Hi all, i have more questions but its all about variables so lets begin
1st, is possible to list all variables ?
Command env display only shell variables, but what if i declared another variable? Command set display more variables but not defined by me.
2nd, what difference is between set... (24 Replies)
Hello,
I'm working on unix with grep (GNU grep) 2.5.1. I'm going through some of the newer regex syntax using Regular Expression Reference - Advanced Syntax a guide.
ls -aLl /bin | grep "\(x\)"
Which works, just highlights 'x' where ever, when ever.
I'm trying to to get (?:) to work but... (4 Replies)
Hi all
I've got a question regarding error handling in shell scripts. My background is mainly object oriented programming languages, but for a year or so I've been doing more and more (bash) shell scripting (which I quite enjoy by the way).
To handle errors in my scripts I... (3 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
I am working on a hands on project. We are creating a script for a corporate phone list. The project I am... (2 Replies)
Hi Folks -
I need help converting a piece of code from batch to bash.
Here is the code:
FOR /f "eol=; tokens=1,2,3,4 delims=, " %%i in (Update_Subvars.txt) do (
ECHO alter database %%i.%%j set variable %%k %%l;
)
What it's doing is retrieving the values from this file:
... (2 Replies)
Hello,
I have a newbe syntax error but I cant find it
syntax error: unexpected end of file
#!/bin/csh
# pe request
#$ -pe mpi_16 32
#### 16 core : 'mpi_16 16' || 24 core : 'mpi_24 24 '
# our Job name
#$ -N test2MD
#$ -S /bin/sh (1 Reply)
Discussion started by: dulceC
1 Replies
LEARN ABOUT POSIX
export
EXPORT(P) POSIX Programmer's Manual EXPORT(P)
NAME
export - set the export attribute for variables
SYNOPSIS
export name[=word]...
export -p
DESCRIPTION
The shell shall give the export attribute to the variables corresponding to the specified names, which shall cause them to be in the envi-
ronment of subsequently executed commands. If the name of a variable is followed by = word, then the value of that variable shall be set to
word.
The export special built-in shall support the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
When -p is specified, export shall write to the standard output the names and values of all exported variables, in the following format:
"export %s=%s
", <name>, <value>
if name is set, and:
"export %s
", <name>
if name is unset.
The shell shall format the output, including the proper use of quoting, so that it is suitable for reinput to the shell as commands that
achieve the same exporting results, except:
1. Read-only variables with values cannot be reset.
2. Variables that were unset at the time they were output need not be reset to the unset state if a value is assigned to the variable
between the time the state was saved and the time at which the saved output is reinput to the shell.
When no arguments are given, the results are unspecified.
OPTIONS
See the DESCRIPTION.
OPERANDS
See the DESCRIPTION.
STDIN
Not used.
INPUT FILES
None.
ENVIRONMENT VARIABLES
None.
ASYNCHRONOUS EVENTS
Default.
STDOUT
See the DESCRIPTION.
STDERR
The standard error shall be used only for diagnostic messages.
OUTPUT FILES
None.
EXTENDED DESCRIPTION
None.
EXIT STATUS
Zero.
CONSEQUENCES OF ERRORS
Default.
The following sections are informative.
APPLICATION USAGE
None.
EXAMPLES
Export PWD and HOME variables:
export PWD HOME
Set and export the PATH variable:
export PATH=/local/bin:$PATH
Save and restore all exported variables:
export -p > temp-fileunset a lot of variables... processing. temp-file
RATIONALE
Some historical shells use the no-argument case as the functional equivalent of what is required here with -p. This feature was left
unspecified because it is not historical practice in all shells, and some scripts may rely on the now-unspecified results on their imple-
mentations. Attempts to specify the -p output as the default case were unsuccessful in achieving consensus. The -p option was added to
allow portable access to the values that can be saved and then later restored using; for example, a dot script.
FUTURE DIRECTIONS
None.
SEE ALSO
Special Built-In Utilities
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE
and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained
online at http://www.opengroup.org/unix/online.html .
IEEE /The Open Group 2003 EXPORT(P)
10-18-2010
