awk - using variables in pattern which contain full pathname
Hello.
I would like to make this bash command working.
In the following code, the bash variable 'ZYPPER_LOCAL_REP' contain a full pathname like '/path/to/path/somewhere'
I run into problems because of the use of a bash variables and because the variable contain a string with some '/'
With C Shell you can get the root, head, tail and extension of a pathname by using pathname variable modifiers.
Example Script:
#! /bin/csh
set pathvar=/home/WSJ091305.txt
echo $pathvar:r
echo $pathvar:h
echo $pathvar:t
echo $pathvar:e
The result of executing this script is:
... (7 Replies)
Hi! I need to get PID of some particular process and I wonder if I can use pgrep tool for this purpose. The problem is that pgrep doesn't perform pattern matching on the whole command line, even if I use -f key. Parsing output of ps command is not quite convenient... Also deamon, which PID I need... (2 Replies)
How would I get folders owned by specific users.. I want to pass users as a shell variable to awk.
drwxr-x--x 3 user1 allusers 512 Oct 14 2006 946157019/
drwxr-x--x 3 user2 allusers 512 Mar 9 2008 94825883/
drwxr-x--x 3 user3 allusers 512 Mar 9 2008 948390501/
... (3 Replies)
How to to pass variable to the below awk command
I would like to pass variables to the awk command instead of the constants "a/cc" but I don't know exactly the correct syntax
awk '/a/,/cc/' temp1.out
file.txt
a
b
s
cc
g
d
output
a
b
s (8 Replies)
I am trying to print text between two variables in a file
I have tried the following things but none seem to work:
awk ' /'$a'/ {flag=1;next} /'$b'/{flag=0} flag { print }' file
and also
sed "/$a/,/$b/p" file
But none seem to work
Any Ideas?
Thanks in Advance (5 Replies)
Hi,
I need to extract all the content between two strings stored in two variables "startstring" and "endstring"
startstring=hello
enstring=world
#notworking
awk '/$startstring/, $NF ~ /$endstring/ ' file > file2
The above code is not working with variables. It works when actual string... (2 Replies)
I am running an awk to verify all the memory settings for tomcat, and need to include path or directory in output ....
I am running:
awk '{ print $3 }' /opt/dir1/dir2/*/tomcat/bin/setenv.sh
Output results:
-Xms1024m
-Xmx1536m
-Xmx1536m
-Xmx1024m
-Xms1024m
-Xms1024m
-Xms512m
-Xms1024m... (3 Replies)
Hi,
I need to do find and replace, but the pattern is not full known.
for example,
my file has /proj/app-d1/sun or /data/site-d1/conf
here app-d1 and site-d1 is not constant. It may be different in different files. common part is /proj/xx/sun and /data/xxx/conf
i want to find where ever... (6 Replies)
Hello.
Question 1 :
I want to comment out all lines of a cron file which are not already commented out for each full path pattern matched.
Example 1 nothing to do because line is already commented out; pattern = '/usr/bin/munin-cron'
# */5 * * * * munin test -x... (3 Replies)
Discussion started by: jcdole
3 Replies
LEARN ABOUT CENTOS
git-check-ignore
GIT-CHECK-IGNORE(1) Git Manual GIT-CHECK-IGNORE(1)NAME
git-check-ignore - Debug gitignore / exclude files
SYNOPSIS
git check-ignore [options] pathname...
git check-ignore [options] --stdin < <list-of-paths>
DESCRIPTION
For each pathname given via the command-line or from a file via --stdin, show the pattern from .gitignore (or other input files to the
exclude mechanism) that decides if the pathname is excluded or included. Later patterns within a file take precedence over earlier ones.
OPTIONS -q, --quiet
Don't output anything, just set exit status. This is only valid with a single pathname.
-v, --verbose
Also output details about the matching pattern (if any) for each given pathname.
--stdin
Read file names from stdin instead of from the command-line.
-z
The output format is modified to be machine-parseable (see below). If --stdin is also given, input paths are separated with a NUL
character instead of a linefeed character.
OUTPUT
By default, any of the given pathnames which match an ignore pattern will be output, one per line. If no pattern matches a given path,
nothing will be output for that path; this means that path will not be ignored.
If --verbose is specified, the output is a series of lines of the form:
<source> <COLON> <linenum> <COLON> <pattern> <HT> <pathname>
<pathname> is the path of a file being queried, <pattern> is the matching pattern, <source> is the pattern's source file, and <linenum> is
the line number of the pattern within that source. If the pattern contained a ! prefix or / suffix, it will be preserved in the output.
<source> will be an absolute path when referring to the file configured by core.excludesfile, or relative to the repository root when
referring to .git/info/exclude or a per-directory exclude file.
If -z is specified, the pathnames in the output are delimited by the null character; if --verbose is also specified then null characters
are also used instead of colons and hard tabs:
<source> <NULL> <linenum> <NULL> <pattern> <NULL> <pathname> <NULL>
EXIT STATUS
0
One or more of the provided paths is ignored.
1
None of the provided paths are ignored.
128
A fatal error was encountered.
SEE ALSO gitignore(5)gitconfig(5)git-ls-files(5)GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-CHECK-IGNORE(1)