04-20-2011
Thanks Corona688, I had already tried that and found that it would not work because eval attempts to
execute the string, but the string is not a command, just a bunch of dash options, e.g.:
script: line 4: eval: -a: invalid option
eval: usage: eval [arg ...]
However you did give me an idea which does work (and I think does not have security issues)...
opts="$(eval echo $opts) $*"
So thanks again!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all-
I have a variable that contains a web page:
echo $STUFF
<html> <head> <title>my page</title></head> <body> blah blah etc..
Can I use the shell's parameter expansion abilities to remove just the tags?
I thought that FIXHTML=${STUFF//<*>/} might do it, but it didn't seem to... (2 Replies)
Discussion started by: rev66
2 Replies
2. Shell Programming and Scripting
Say you have this numeric variable that can be set by the user but you never want it to leave a certain range when it gets printed. How could you use parameter expansion such that it will never expand outside of that boundary? Thanks
---------- Post updated at 11:09 PM ---------- Previous update... (3 Replies)
Discussion started by: stevenswj
3 Replies
3. Shell Programming and Scripting
I'm trying to write a script that parses my music collection and hard link some filenames that my media player doesn't like to other names.
To do this I need to extract the name and remove alla non ASCII characters from that and do a cp -l with the result.
Problem is this:
22:16:58 $... (8 Replies)
Discussion started by: refuser
8 Replies
4. UNIX for Dummies Questions & Answers
Hello experts,
I am exploring parameter expansion, and trying to cut the fields in a URL.
Following is the requirement:
I have
// abc.nnt /dir1/dir2/dir3/dir4/somefile.java
What i need to get is the path after dir3, and dir3 will be passed.
output that i need is... (1 Reply)
Discussion started by: gjarms
1 Replies
5. Shell Programming and Scripting
I have made the following examples that print various parameter expansions
text: iv-hhz-sac/hpac/hhz.d/iv.hpac..hhz.d.2016.250.070018.sac
(text%.*): iv-hhz-sac/hpac/hhz.d/iv.hpac..hhz.d.2016.250.070018
(text%%.*): iv-hhz-sac/hpac/hhz
(text#*.): d/iv.hpac..hhz.d.2016.250.070018.sac... (2 Replies)
Discussion started by: kristinu
2 Replies
6. Shell Programming and Scripting
#!/bin/bash
SNMPW='/usr/bin/snmpwalk'
while read h i
do
loc=$($SNMPW -v3 -u 'Myusername' -l authPriv -a SHA -A 'Password1' -x AES -X 'Password2' $i sysLocation.0 2>/dev/null)
loc=${loc:-" is not snmpable."}
loc=${loc##*: }
loc=${loc//,/}
echo "$i,$h,$loc"
done < $1
My question is ... ... (1 Reply)
Discussion started by: sumguy
1 Replies
7. Shell Programming and Scripting
I am trying to become more fluent with the interworking of bash and minimize the number of external calls.
Sample Data. This will be the response of the snmp query.
SNMPv2-MIB::sysName.0 = STRING: SomeHostName
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.1.1745... (5 Replies)
Discussion started by: sumguy
5 Replies
8. UNIX for Beginners Questions & Answers
Currently i am building one script to grep region records in the config file based on parameter and then i am creating a text file with that out put and i am reading the source file path in that out put file
now i need to pass one more parameter like module based upon that it has to create a... (1 Reply)
Discussion started by: saranath
1 Replies
9. Shell Programming and Scripting
Example data
$ ls *somehost*
10.10.10.10_somehost1.xyz.com.log
11.11.11.11_somehost2.xyz.com.log
#!/bin/bash
#FILES="*.log"
FILES=${FILES:-*.log}
for x in $FILES
do
ip="${x%%_*}" # isolate IP address
x="${x##*_}" # isolate hostname
hnam="${x%.*}" # Remove the ".log"... (2 Replies)
Discussion started by: popeye
2 Replies
10. Shell Programming and Scripting
Hello All,
Could you please do help me here as I would like to perform parameter expansion in shell over a parameter expansion.
Let's say I have following variable.
path="/var/talend/nat/cdc"
Now to get only nat I could do following.
path1="${path%/*}"
path1="${path1##*/}"
Here... (8 Replies)
Discussion started by: RavinderSingh13
8 Replies
LEARN ABOUT HPUX
rc.config
rc.config(4) Kernel Interfaces Manual rc.config(4)
NAME
rc.config, rc.config.d - files containing system configuration information
SYNOPSIS
DESCRIPTION
The system configuration used at startup is contained in files within the directory The file sources all of the files within and and
exports their contents to the environment.
/etc/rc.config
The file is a script that sources all of the scripts, and also sources To read the configuration definitions, only this file need be
sourced. This file is sourced by whenever it is run, such as when the command is run to transition between run states. Each file that
exists in is sourced, without regard to which startup scripts are to be executed.
/etc/rc.config.d
The configuration information is structured as a directory of files, rather than as a single file containing the same information. This
allows developers to create and manage their own configuration files here, without the complications of shared ownership and access of a
common file.
/etc/rc.config.d/* Files
This is where files containing configuration variable assignments are located.
Configuration scripts must be written to be read by the POSIX shell, and not the Bourne shell, or In some cases, these files must also be
read and possibly modified by control scripts or the sam program. See sd(4) and sam(1M). For this reason, each variable definition must
appear on a separate line, with the syntax:
No trailing comments may appear on a variable definition line. Comment statements must be on separate lines, with the comment character in
column one. This example shows the required syntax for configuration files:
Configuration variables may be declared as array parameters when describing multiple instances of the variable configuration. For example,
a system may contain two network interfaces, each having a unique IP address and subnet mask (see ifconfig(1M)). An example of such a dec-
laration is as follows:
Note that there must be no requirements on the order of the files sourced. This means configuration files must not refer to variables
defined in other configuration files, since there is no guarantee that the variable being referenced is currently defined. There is no
protection against environment variable namespace collision in these configuration files. Programmers must take care to avoid such prob-
lems.
/etc/TIMEZONE
The file contains the definition of the environment variable. This file is required by POSIX. It is sourced by at the same time the files
are sourced.
SEE ALSO
rc(1M).
rc.config(4)