Not clear. What is the problem?
- Do you want to eliminate eval?
- Does the overall logics not deliver what you need? Please be aware that a chain -o (OR operators) stops after the first to evaluate to TRUE.
- How are the two code snippets in above related? What and/or where is filter 5?
- Why does filter 2 work in the first snippet but doesn't in the second.
Additional: if $MY_PATH has the potential to contain whitespace it gets a little more tricky. After some mucking around I did find this solution in bash using arrays:
Given that there is no way to know what files might be present in the directory in which this script might be run, to guarantee that you won't get a syntax error in find if .direct* or .xsession* expand to more than one filename, and to guarantee that all files with the desired names will be matched if either of those patterns match a single filename in the current directory, I think it would be safer to change:
>- Do you want to eliminate eval?
yes.
I use { CMD="..." /// echo "$CMD" /// eval "$CMD" } when debuging scripts.
>- Does the overall logics not deliver what you need? Please be aware that a chain >-o (OR operators) stops after the first to evaluate to TRUE.
In brief I need this command :
find "path" "list of directories to ignore" and "list files to ignore" "pass result to function"
find "path" "FILTER_1" some_operator "FILTER_2" "pass result to function"
I want to ignore all directories enumerated in filter 1 (this work)
FILTER_1 is a list of directories
I want to ignore all files enumerated in filter 2 (this does not work together with FILTER_1)
FILTER_2 is a list of files
-name pattern
Base of file name (the path with the leading directories removed) matches shell
pattern pattern. Because the leading directories are removed, the file names
considered for a match with -name will never include a slash, so `-name a/b'
will never match anything (you probably need to use -path instead). The
metacharacters (`*', `?', and `[]') match a `.' at the start of the base name
(this is a change in findutils-4.2.2; see section STANDARDS CONFORMANCE below).
To ignore a directory and the files under it, use -prune; see an example in the
description of -path. Braces are not recognised as being special, despite the
fact that some shells including Bash imbue braces with a special meaning in
shell patterns. The filename matching is performed with the use of the
fnmatch(3) library function. Don't forget to enclose the pattern in quotes in
order to protect it from expansion by the shell.
---------- Post updated at 12:12 ---------- Previous update was at 12:02 ----------
Thank you very much for your effort.
But I have to draw your attention on two things :
1°) FILTER_2 is a list of files and then ".Xauthority,.xsession1,.bash_history" are files.
2°) My real problem is when I try to add a second predicate (list of files in FILTER_2) after the first predicate ( FILTER_1 )
---------- Post updated at 12:24 ---------- Previous update was at 12:12 ----------
Quote:
Originally Posted by Don Cragun
Given that there is no way to know what files might be present in the directory in which this script might be run, to guarantee that you won't get a syntax error in find if .direct* or .xsession* expand to more than one filename, and to guarantee that all files with the desired names will be matched if either of those patterns match a single filename in the current directory ...............
If I run my command with FILTER_2 alone like this :
Given that there is no way to know what files might be present in the directory in which this script might be run, to guarantee that you won't get a syntax error in find if .direct* or .xsession* expand to more than one filename, and to guarantee that all files with the desired names will be matched if either of those patterns match a single filename in the current directory, I think it would be safer to change:
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)
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)
#!/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)
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)
This is what I have in my directory.
$ ls
test1.txt test2.txt test3.txt test4.txt test5.txt test_script.sh
This is what my shellscript looks like.
#!/bin/bash
for filename in /shell_expansion/*.txt; do
for ((i=0; i<=3; i++)); do
echo "$filename"
... (5 Replies)
Hello,
is there a kind soul who can answer me, does the SH support double substitution known as indirect expansion similar to BASH? The syntax for bash is ${!var}.
For instance in bash I can write something like this:
VAR="value"
REF_VAR="VAR"
echo ${!REF_VAR}
and get the "value"... (1 Reply)
i write a batch file , here is the content.
dirname='date +%Y-%m-%d'
mkdir dirname
but it doen's work, it just create a folder named date and +%Y-%m-%d.
i have tried run the command seperately in the bash prompt. after the first
sentence executed , i use $dirname to watch the value of... (4 Replies)
I have a script that takes an option for server pools to run the script against. The option is given as a comma separated list (ie, -p 201,204,301).
I'm using eval and brace expansion to get those pool numbers into an array. It works fine unless only 1 pool number is given. Here's the code:
... (5 Replies)
Hello -
I have a bash script which does some logging, and I'd like to include the line number of the echo statement that pipes into $LOGGER:
MYPID=$$
MYNAME=`basename $0`
LOGGER="/usr/bin/logger -t $MYNAME($LINENO) -p daemon.error"
...
echo 'this is an entry into the log file' | $LOGGER
... (3 Replies)
