10-05-2014
Quote:
Originally Posted by
cokedude
Can you please explain this part? I don't understand the purpose of a "~" here and why you had to the a.out in "//" . Would bash try to expand the "." if you didn't "\" it?
awk '$4 ~ /a\.out/ It is a matching pattern evaluation.
Let
/pattern/ where pattern is a regular expression, therefore a `.' would match any character except the newline, thus the escape `\' to make it match just a single period character.
Last edited by Aia; 10-06-2014 at 12:17 AM..
Reason: mispelling
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
i have a very short file that has in it a line for a find command.
now, when i run this script and I kill the script later, using the ps -ef | grep scriptname. i noticed kill -9 kills the script itself but does not kill the internal find command that it gave birth to.
say theres a file... (0 Replies)
Discussion started by: Terrible
0 Replies
2. UNIX for Dummies Questions & Answers
Hello,
ps -C a*
returns the list of the process I need to kill.
but
ps -C a* -o pid | kill
does not work and I can't get the syntax right.
Thanks for any help (4 Replies)
Discussion started by: JCR
4 Replies
3. Shell Programming and Scripting
Hi guys,
I am new to Unix shell scripting. Can anyone of you tell me how to kill all the processes at a time for a particular user?(No listing the process ID of each process in the kill -9 command).
Thanks in Advance,
-Hary (5 Replies)
Discussion started by: tadi18
5 Replies
4. Solaris
mqm 17700 16815 0 0:00 <defunct>
kill -9 does not work, even as root (10 Replies)
Discussion started by: csaunders
10 Replies
5. Solaris
how to kill the processes of aperticular user?
because i have nearly 25000 process are there for perticular user. i need to kill.
Please provide the information?
Regards,
Rajesh (3 Replies)
Discussion started by: pmrajesh21
3 Replies
6. HP-UX
Hi,
I read a set of processes with:
ps -eaf|grep oracleTRLV
The result is:
oracle 23253 1 0 15:14:11 ? 0:00 oracleTRLV (LOCAL=NO)
oracle 23301 1 0 15:15:07 ? 0:00 oracleTRLV (LOCAL=NO)
oracle 22914 1 0 15:11:19 ? 0:00 oracleTRLV (LOCAL=NO)
How to I kill the "oracleTRLV" ones? Is there... (17 Replies)
Discussion started by: NicoMan
17 Replies
7. Solaris
Hi,
How to kill the processes running under ptree ?
I am noticing lot of processes running under ptree with ssh ? I tried to kill with -9 option which is not working ?
Thanks,
Radhika. (2 Replies)
Discussion started by: radhirk
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am writing korn shell script. My requirement is, i have to kill the parent process and all of its child processes. Can some one please help me on this?
Thanks in advance for your help.. (1 Reply)
Discussion started by: Sheethal
1 Replies
9. Shell Programming and Scripting
for i in 'ps -f | grep textedit'
do
kill $i
done
I wrote this but it wont work.
I am trying to find processes and kill them.
Any help would be welcome. (1 Reply)
Discussion started by: hawaiifiver
1 Replies
10. Shell Programming and Scripting
Want to kill multiple processes by name. for the example below, I want to kill all 'proxy-stagerd_copy' processes.
I tried this but didn't work:
>> ps -ef|grep proxy_copy
root 991 986 0 14:45:34 ? 0:04 proxy-stagerd
root 1003 991 0 14:45:49 ? 0:01... (2 Replies)
Discussion started by: catalinawinemxr
2 Replies
FNMATCH(3) Linux Programmer's Manual FNMATCH(3)
NAME
fnmatch - match filename or pathname
SYNOPSIS
#include <fnmatch.h>
int fnmatch(const char *pattern, const char *string, int flags);
DESCRIPTION
The fnmatch() function checks whether the string argument matches the pattern argument, which is a shell wildcard pattern.
The flags argument modifies the behavior; it is the bitwise OR of zero or more of the following flags:
FNM_NOESCAPE
If this flag is set, treat backslash as an ordinary character, instead of an escape character.
FNM_PATHNAME
If this flag is set, match a slash in string only with a slash in pattern and not by an asterisk (*) or a question mark (?)
metacharacter, nor by a bracket expression ([]) containing a slash.
FNM_PERIOD
If this flag is set, a leading period in string has to be matched exactly by a period in pattern. A period is considered to be
leading if it is the first character in string, or if both FNM_PATHNAME is set and the period immediately follows a slash.
FNM_FILE_NAME
This is a GNU synonym for FNM_PATHNAME.
FNM_LEADING_DIR
If this flag (a GNU extension) is set, the pattern is considered to be matched if it matches an initial segment of string which is
followed by a slash. This flag is mainly for the internal use of glibc and is implemented only in certain cases.
FNM_CASEFOLD
If this flag (a GNU extension) is set, the pattern is matched case-insensitively.
FNM_EXTMATCH
If this flag (a GNU extension) is set, extended patterns are supported, as introduced by 'ksh' and now supported by other shells.
The extended format is as follows, with pattern-list being a '|' separated list of patterns.
'?(pattern-list)'
The pattern matches if zero or one occurrences of any of the patterns in the pattern-list match the input string.
'*(pattern-list)'
The pattern matches if zero or more occurrences of any of the patterns in the pattern-list match the input string.
'+(pattern-list)'
The pattern matches if one or more occurrences of any of the patterns in the pattern-list match the input string.
'@(pattern-list)'
The pattern matches if exactly one occurrence of any of the patterns in the pattern-list match the input string.
'!(pattern-list)'
The pattern matches if the input string cannot be matched with any of the patterns in the pattern-list.
RETURN VALUE
Zero if string matches pattern, FNM_NOMATCH if there is no match or another nonzero value if there is an error.
ATTRIBUTES
For an explanation of the terms used in this section, see attributes(7).
+----------+---------------+--------------------+
|Interface | Attribute | Value |
+----------+---------------+--------------------+
|fnmatch() | Thread safety | MT-Safe env locale |
+----------+---------------+--------------------+
CONFORMING TO
POSIX.1-2001, POSIX.1-2008, POSIX.2. The FNM_FILE_NAME, FNM_LEADING_DIR, and FNM_CASEFOLD flags are GNU extensions.
SEE ALSO
sh(1), glob(3), scandir(3), wordexp(3), glob(7)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
GNU
2015-12-28 FNMATCH(3)