|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
How to Force command substitution evaluation in bash?
Post 302969879 by siegfried on Tuesday 29th of March 2016 01:56:05 PM
03-29-2016
|
|
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
#!/bin/bash
#set -x
MAX=255
FILE=$1.dns_list
#declare -a d_arr
if
then
echo "Usage: `basename $0` network"
echo " e.g.`basename $0` 1.1.1"
exit
fi
echo "Remove file $FILE..."
rm $FILE
for (( i = 1; i < $MAX; i++ ))
do
PARSE=$(host $1.${i})
... (3 Replies)
Discussion started by: flee
3 Replies
2. Shell Programming and Scripting
Is it possible with a bash variable to perform multiple substitution strings to one variable?
I have this variable:
echo $clock
TIMEZONE="US/Central"
What I would like to do with bash only it pull out just the "US" part of the variable.. which could be any number of countries.
this is... (6 Replies)
Discussion started by: trey85stang
6 Replies
3. Shell Programming and Scripting
Hi,
I'm using an array that contains compiler FLAGS
that need to be executed either before ./configure
or after the main 'make' command.
example of array containing compiler flags.
-------------------------------------------------
FLAGS="CFLAGS=\"-arch x86_64 -g -Os -pipe... (7 Replies)
Discussion started by: ASGR
7 Replies
4. Shell Programming and Scripting
Hello!
I'm writing a shell script using #!/bin/bash instead of #!/bin/sh because of the substitution: ${!variable}, which won't work with sh. My main problem is the following (just a summarized example, the script is much more complex):
# sourced from a configuration file, we have a lot of... (6 Replies)
Discussion started by: teresaejunior
6 Replies
5. UNIX for Dummies Questions & Answers
Hi all!
I'm writting one script to copy a file in various folders, but there are 2 things to validate. First that the folder where i'll be cpying exists, and second that i have permissions to copy the file in it.
so far i have found the way to validate the folder exists, but when trying to... (6 Replies)
Discussion started by: feliperivera
6 Replies
6. Shell Programming and Scripting
I have one script calling another with a set of strings that includes white space. Script A calls Script B with these input strings: one two "th ree"
Script B pulls apart the arguments correctly:
arg0 = one, arg1 = two, arg2 = "th ree"
if I call it from within Script A like so:... (10 Replies)
Discussion started by: skippyV
10 Replies
7. Shell Programming and Scripting
I'm building a script that may received start and end date as parameters. I whant to make it as flexible as possible so I'm accepting epoch and date in a way that "date --date=" command may accept. In order to know if parameter provided is an epoc or a "date --date=" string I evaluate if the value... (2 Replies)
Discussion started by: lramirev
2 Replies
8. Shell Programming and Scripting
OK, I'm striving to abide by all the rules this time.
Here is a fragment of my windows10/cygwin64/bash script:
export BUPLOG=$(BackupRecords --log "$src")
robocopy $(BackupRecords -mrbd "$src" --path "$src") $(BackupRecords --appSwitches "$src") "$src" "$dst" $(BackupRecords --fileSwitches... (0 Replies)
Discussion started by: siegfried
0 Replies
9. Shell Programming and Scripting
Could somebody please explain to me why and how the highlighted line(s) (?) of code puts the "test" evaluation into "result" and then to $enable_static ? Or does not ?
I did comment out the original code and changed it to what I feel is less cryptic , but the "result" is still wrong =... (3 Replies)
Discussion started by: anne
3 Replies
LEARN ABOUT OSF1
lsmsad
lsmsad(8) System Manager's Manual lsmsad(8) NAME
lsmsad - Starts the Storage Administrator (SA) daemon SYNOPSIS
/usr/sbin/lsmsad DESCRIPTION
The SA daemon, lsmsad, is a process required by lsmsa, the SA graphical user interface (GUI). The daemon issues commands and obtains system information on behalf of SA. The SA daemon runs on a Tru64 UNIX system on which LSM is initialized and running. The SA client runs on any machine that supports the Java Runtime Environment. The SA daemon is automatically started at boot time. Under normal conditions, the daemon does not need to be run manually. If SA does not start during the boot process, enter: /sbin/init.d/lsmsa stop To restart SA, enter: /sbin/init.d/lsmsa start Only one SA daemon can be running on a system at a given time. If a second SA daemon attempts to start, it will fail. RESTRICTIONS
You must be root user to run lsmsad. FILES
The script that starts lsmsad at boot time. The command log file that tracks SA tasks. The access log file that tracks login to SA. The server log file that tracks server startup information and server errors. The log maintenance shell script that saves and compresses log files. SEE ALSO
lsmsa(8), volintro(8) lsmsad(8)