12-03-2014
I apologize. I don't use zsh. I had assumed that it was rejecting the old form of command substitution, but zsh (at least on OS X) does not seem to perform field splitting as required by the standards on the unquoted expansion of a variable. Do you have to use zsh for your script instead of running the entire script with bash or ksh?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a command which will run fine in a unix command prompt. Can you tell how to interprete this command inside perl script......
The command is :
perl -pe 's/(\|333\}.*)\}$/$1|1.6}/' FIA.txt
This will search for the number 333 and appends 1.6 at the end of that line....... (1 Reply)
Discussion started by: vinay123
1 Replies
2. Shell Programming and Scripting
Hi,
I have a problem with '.zlogout' not being run on Solaris 10.
Here's whats happening.
I remotely log in from a PC running Cygwin/X using a local xterm window and ssh to start a remote 'zsh' shell, version 4.2.5, on a Solaris 10 server.
The Server has KDE installed but as a Window... (0 Replies)
Discussion started by: stv_t
0 Replies
3. Shell Programming and Scripting
Hi everyone,
when executing this command in unix:
echo "WM7 Fatal Alerts:", $(cat query1.txt) > a.csvIt works fine, but running this command in a shell script gives an error saying that there's a syntax error.
here is content of my script:
tdbsrvr$ vi hc.sh
"hc.sh" 22 lines, 509... (4 Replies)
Discussion started by: 4dirk1
4 Replies
4. Shell Programming and Scripting
Hi everyone,
I'm echo some text with extended ascii characters as below:
echo -e "Pr\xE9sentation du spectacle" > output
or
echo -e "Présentation du spectacle" > outputIf I open the file created I see this text
Présentation du spectacleThe text is shown correctly in this created file when... (7 Replies)
Discussion started by: Ophiuchus
7 Replies
5. Shell Programming and Scripting
There's a JavaScript file that I call from command line (there's a framework) like so:
./RunDiag.js param1:'string one here' param2:'string two here'
I have a shell script where I invoke the above command. I can run it in a script as simple as this
#!/bin/bash
stuff="./RunDiag.js... (4 Replies)
Discussion started by: AcerAspirant
4 Replies
6. Shell Programming and Scripting
I have bash shell script which is internally calling python script.I would like to know how long python is taking to execute.I am not allowed to do changes in python script.Please note i need to know execution time of python script which is getting executed inside shell .I need to store execution... (2 Replies)
Discussion started by: Adfire
2 Replies
7. Shell Programming and Scripting
Hello,
Just wondered if there is any possibility to run a command at sharp time inside a script in linux. My question is not about crontab
Example:
#!/bin/bash
cd /home/database
for i in *
do
command 1
if time is 19:00, day is Monday then run command2
if time is 20:00, day is... (10 Replies)
Discussion started by: baris35
10 Replies
8. Shell Programming and Scripting
How to run several bash commands put in bash command line without needing and requiring a script file.
Because I'm actually a windows guy and new here so for illustration is sort of :
$ bash "echo ${PATH} & echo have a nice day!"
will do output, for example:... (4 Replies)
Discussion started by: abdulbadii
4 Replies
9. Shell Programming and Scripting
I want to run commands inside a bash script.
An example is
I want to pass the command in a string as regexp as an argument to the script, then run sed on the bash variable
sed.sh regexp
sed.sh "-i \"s/<p>//g\""
then call
sed "$regexp" $fl (3 Replies)
Discussion started by: Kangol
3 Replies
10. UNIX for Advanced & Expert Users
I am trying to run an awk command inside of ssh and it is not working. These are AIX servers.
for i in `cat servers`; do ssh $i "/bin/hostname; df -g | awk '/dev/ && $4+0 > 70'"; done
server1
server2
server3
server4
I also tried these two methods and they did not work. It just seemed... (5 Replies)
Discussion started by: cokedude
5 Replies
LEARN ABOUT OPENSOLARIS
readonly
readonly(1) User Commands readonly(1)
NAME
readonly - shell built-in function to protect the value of the given variable from reassignment
SYNOPSIS
sh
readonly [name]...
ksh
**readonly [name [= value]]...
**readonly -p
ksh93
++readonly [-p] [name [= value]]...
DESCRIPTION
sh
The given names are marked readonly and the values of the these names may not be changed by subsequent assignment. If no arguments are
given, a list of all readonly names is printed.
ksh
The given names are marked readonly and these names cannot be changed by subsequent assignment.
When -p is specified, readonly writes to the standard output the names and values of all read-only variables, in the following format:
"readonly %s=%s
", name, value
if name is set, and:
"readonly $s
", name
if name is unset.
The shell formats the output, including the proper use of quoting, so that it is suitable for reinput to the shell as commands that achieve
the same value and readonly attribute-setting results in a shell execution environment in which:
1. Variables with values set at the time they were output do not have the readonly attribute set.
2. Variables that were unset at the time they were output do not have a value at the time at which the saved output is re-input to
the shell.
On this manual page, ksh(1) commands that are preceded by one or two ** (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a
variable assignment. This means that tilde substitution is performed after the = sign and word splitting and file name genera-
tion are not performed.
ksh93
readonly sets the readonly attribute on each of the variables specified by name which prevents their values from being changed. If =value
is specified, the variable name is set to value before the variable is made readonly.
If no names are specified then the names and values of all readonly variables are written to standard output.
readonly is built-in to the shell as a declaration command so that field splitting and pathname expansion are not performed on the argu-
ments. Tilde expansion occurs on value.
-p Causes the output to be in a form of readonly commands that can be used as input to the shell to recreate the current set of readonly
variables.
On this manual page, ksh93(1) commands that are preceded by one or two + symbols are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. They are not valid function names.
5. Words, following a command preceded by ++ that are in the format of a variable assignment, are expanded with the same rules as a
variable assignment. This means that tilde substitution is performed after the = sign and field splitting and file name genera-
tion are not performed.
EXIT STATUS
ksh93
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
ksh(1), ksh93(1), sh(1), typeset(1), attributes(5)
SunOS 5.11 2 Nov 2007 readonly(1)