05-27-2015
AKA lazy matching as opposed to greedy matching
This User Gave Thanks to Scrutinizer For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
i can only find the first occurance of a pattern how do i set it to loop untill all occurances have changed.
#! /usr/bin/perl
use POSIX;
open (DFH_FILE, "./dfh") or die "Can not read file ($!)";
foreach (<DFH_FILE>) {
if ($_ !~ /^#|^$/) {
chomp;
... (1 Reply)
Discussion started by: Optimus_P
1 Replies
2. Shell Programming and Scripting
hi i am trying to get digits inside brackes from file , whose structure is defined below
CREATE TABLE TELM
(SOC_NO CHAR (3) NOT NULL,
TXN_AMOUNT NUMBER (17,3)
SIGN_ON_TIME CHAR (8)
TELLER_APP_LIMIT NUMBER (17,3)
FIL01 ... (2 Replies)
Discussion started by: zedex
2 Replies
3. Shell Programming and Scripting
Hello
I got the below one from in one of this forums
For Ex: Loading File System Networking in nature
now i need to extract the patterns between the words File and Networking :
i.e. sample output: System
cmd used : cat <file> | sed 's/.*File //' | sed 's/Closing.*$//'
Actually... (0 Replies)
Discussion started by: maxmave
0 Replies
4. Shell Programming and Scripting
Hi,
I got doubt in Pattern matching, could you tell me how the following differs in action ??
if ( $line1==/$line2/ )
if ( $line1=~/$line2/ )
if ( $line1=~m/$line2/)
What is the significance of '~' in matching.
Thanks in advance
CoolBhai (5 Replies)
Discussion started by: coolbhai
5 Replies
5. Shell Programming and Scripting
Hello experts,
I have a file containing the following text(shortened here).
File Begin
----------
< # Billboard.d3fc1302a677.imagePath=S:\\efcm_T4
< Billboard.d3fc1302a677.imagePath=S:\\efcm_T4
---
> # Billboard.d3fc1302a677.imagePath=S:\\efcm_Cassini
>... (2 Replies)
Discussion started by: nmattam
2 Replies
6. Shell Programming and Scripting
Hi experts,
I have many occurances of the following headers in a file. I need to grep for the word changed/inserted in the header, calculate the difference between the two numbers and list the count incrementally.
Headers in a file look like this:
-------------------
---------------------... (6 Replies)
Discussion started by: nmattam
6 Replies
7. Shell Programming and Scripting
I am doing a file patterhn matching for a text file in PERL
I am using this,,, but it says that no file is found
$filepattern = '\d{1,4}.*A0NW9693.NDM.HBIDT.*.AD34XADJ.txt';
Can anyone help me out with Perl Pattern Matching concepts and how to do pattern matching for this txt file:... (4 Replies)
Discussion started by: msrahman
4 Replies
8. Shell Programming and Scripting
I have a 2 files in .gz format and it consists of 5 million lines the format of the file would be
gzcat file1.gz | more
abcde
aerere
ffgh56
..
..
12345
gzcat file2.gz | more
abcde , 12345 , 67890,
ffgh56 , 45623 ,12334
whatever the string is in the file1 should be matched... (3 Replies)
Discussion started by: aravindj80
3 Replies
9. Shell Programming and Scripting
My log file looks as given below, its actually a huge file around 1 GB and these are some of the line:
conn=5368758 op=10628050 msgId=64 - RESULT err=0 tag=101 nentries=1 etime=0
conn=7462122 op=-1 msgId=-1 - fd=247 slot=247 LDAPS connection from 10.13.18.12:37645 to 10.18.6.45
conn=7462122... (5 Replies)
Discussion started by: sags007_99
5 Replies
10. Shell Programming and Scripting
Hi,
I have a list of IP, eg :
192.168.0.15
192.168.0.24
192.168.2.110
192.168.2.200
And I would like the shortest pattern who match with '192.168.0' and '192.168.2' (without the last dot and number). (7 Replies)
Discussion started by: X-Or
7 Replies
LEARN ABOUT MOJAVE
killall
KILLALL(1) BSD General Commands Manual KILLALL(1)
NAME
killall -- kill processes by name
SYNOPSIS
killall [-delmsvz] [-help] [-u user] [-t tty] [-c procname] [-SIGNAL] [procname ...]
DESCRIPTION
The killall utility kills processes selected by name, as opposed to the selection by pid as done by kill(1). By default, it will send a TERM
signal to all processes with a real UID identical to the caller of killall that match the name procname. The super-user is allowed to kill
any process.
The options are as follows:
-v Be more verbose about what will be done.
-e Use the effective user ID instead of the (default) real user ID for matching processes specified with the -u option.
-help Give a help on the command usage and exit.
-l List the names of the available signals and exit, like in kill(1).
-m Match the argument procname as a (case sensitive) regular expression against the names of processes found. CAUTION! This
is dangerous, a single dot will match any process running under the real UID of the caller.
-s Show only what would be done, but do not send any signal.
-d Print detailed information about the processes matched, but do not send any signal.
-SIGNAL Send a different signal instead of the default TERM. The signal may be specified either as a name (with or without a lead-
ing SIG), or numerically.
-u user Limit potentially matching processes to those belonging to the specified user.
-t tty Limit potentially matching processes to those running on the specified tty.
-c procname
When used with the -u or -t flags, limit potentially matching processes to those matching the specified procname.
-z Do not skip zombies. This should not have any effect except to print a few error messages if there are zombie processes
that match the specified pattern.
ALL PROCESSES
Sending a signal to all processes with uid XYZ is already supported by kill(1). So use kill(1) for this job (e.g. $ kill -TERM -1 or as root
$ echo kill -TERM -1 | su -m <user>)
EXIT STATUS
The killall command will respond with a short usage message and exit with a status of 2 in case of a command error. A status of 1 will be
returned if either no matching process has been found or not all processes have been signalled successfully. Otherwise, a status of 0 will
be returned.
DIAGNOSTICS
Diagnostic messages will only be printed if requested by -d options.
SEE ALSO
kill(1), sysctl(3)
HISTORY
The killall command appeared in FreeBSD 2.1. It has been modeled after the killall command as available on other platforms.
AUTHORS
The killall program was originally written in Perl and was contributed by Wolfram Schneider, this manual page has been written by Jorg
Wunsch. The current version of killall was rewritten in C by Peter Wemm using sysctl(3).
BSD
January 26, 2004 BSD