I have a situation where I need to search for multiple strings (error messages) such as 'aborted' 'file not found' etc in directory having logs. I have put all the error messages in a text file and using the command.
I'm doing this thru a script where I have a loop which will get the file name to be grepped and search for the messages. If ound I need to display the file which contains the pattern.
During exeuction I have the error as follows:
Can somebody help what could be wrong here..
This is the piece of code
Last edited by zaxxon; 02-25-2010 at 05:10 AM..
Reason: use code tags please, ty
I am using a DEC ALPHA running Digital UNIX (formly DEC OSF/1) and ksh. I have a directory with hundreds of files that only share the extension .rpt. I would like to search that directory based on serial number and operation number and only files that meet both requirements to be printed out. I... (6 Replies)
Hi All,
I have written the below script that searches for the pattern in a file and delete them if present. please can some one have a look and suggest the changes in the script.
#!bin/sh
# The pattern that user want to add to the files
echo "Enter the pattern of the redirect"
read... (4 Replies)
Hi Gurus,
I have a file say for ex. file1 which has 3500 lines in it which are different account numbers and another file (file2) which has 230000 lines in it. I want to read all the lines in file1 and delete all those lines from file2 which has that same pattern as in file1. I am not quite... (4 Replies)
Hi,
I want to list the files containing a no of pattern
like for single string i can use
grep -l "string" *
This command will enlist the files containg this string. Similarly i would like to use for multiple string.
I like to enlist file names having string1 and string 2
Can... (3 Replies)
Hi All,
I have a file in which i have to search for a pattern from the beginning of the file and if the pattern is found , then i have to perform a reverse search from that line to the beginning of the file to get the first occurrence of another pattern.
sample input file
hey
what are you... (8 Replies)
Hi,
I have to write one script that has to search a list of numbers in certain zipped files.
For eg. one file file1.txt contains the numbers. File1.txt contains 5,00,000 numbers and I have to search each number in zipped files(The number of zipped files are around 1000 each file is 5 MB)
I have... (10 Replies)
Hi,
I have code like:
Output it is comming as:
Rels: WM2
Rels: WG2
Rels: 5
- pre/prods.pl
Rels: 6
Rels: 7
Rels: 8
Rels: 10
Rels: Int
But i want only "Rels: 5" pattern Just above "- pre/prods.pl".
By... (7 Replies)
Hi,
We have created a script that would accept the an indicator as a parameter and archive files present in a directory. The indicator would drive what the name pattern of the files to be archived should be.
If the indicator is 1, then the pattern to look out for is FACT*.
If the indicator is... (2 Replies)
Hello,
I have attached 2 files
1) Original_table_definition.txt => which has definition of 3 tables
2) describe_table_output.txt => which has again 3 tables definition gotten thorugh doing a show table or describe table way.
Now difference between 3 tables are that tablea has no... (2 Replies)
Discussion started by: nv186000
2 Replies
LEARN ABOUT DEBIAN
notmuch-search-terms
NOTMUCH-SEARCH-TERMS(7) Miscellaneous Information Manual NOTMUCH-SEARCH-TERMS(7)NAME
notmuch-search-terms - Syntax for notmuch queries
SYNOPSIS
notmuch count [options...] <search-term>...
notmuch dump [ <filename> ] [--] [ <search-term>...]
notmuch search [options...] <search-term>...
notmuch show [options...] <search-term>...
notmuch tag +<tag>|-<tag> [...] [--] <search-term>...
DESCRIPTION
Several notmuch commands accept a common syntax for search terms.
The search terms can consist of free-form text (and quoted phrases) which will match all messages that contain all of the given
terms/phrases in the body, the subject, or any of the sender or recipient headers.
As a special case, a search string consisting of exactly a single asterisk ("*") will match all messages.
In addition to free text, the following prefixes can be used to force terms to match against specific portions of an email, (where <brack-
ets> indicate user-supplied values):
from:<name-or-address>
to:<name-or-address>
subject:<word-or-quoted-phrase>
attachment:<word>
tag:<tag> (or is:<tag>)
id:<message-id>
thread:<thread-id>
folder:<directory-path>
The from: prefix is used to match the name or address of the sender of an email message.
The to: prefix is used to match the names or addresses of any recipient of an email message, (whether To, Cc, or Bcc).
Any term prefixed with subject: will match only text from the subject of an email. Searching for a phrase in the subject is supported by
including quotation marks around the phrase, immediately following subject:.
The attachment: prefix can be used to search for specific filenames (or extensions) of attachments to email messages.
For tag: and is: valid tag values include inbox and unread by default for new messages added by notmuch new as well as any other tag values
added manually with notmuch tag.
For id:, message ID values are the literal contents of the Message-ID: header of email messages, but without the '<', '>' delimiters.
The thread: prefix can be used with the thread ID values that are generated internally by notmuch (and do not appear in email messages).
These thread ID values can be seen in the first column of output from notmuch search
The folder: prefix can be used to search for email message files that are contained within particular directories within the mail store.
Only the directory components below the top-level mail database path are available to be searched.
In addition to individual terms, multiple terms can be combined with Boolean operators ( and, or, not , etc.). Each term in the query will
be implicitly connected by a logical AND if no explicit operator is provided, (except that terms with a common prefix will be implicitly
combined with OR until we get Xapian defect #402 fixed).
Parentheses can also be used to control the combination of the Boolean operators, but will have to be protected from interpretation by the
shell, (such as by putting quotation marks around any parenthesized expression).
Finally, results can be restricted to only messages within a particular time range, (based on the Date: header) with a syntax of:
<initial-timestamp>..<final-timestamp>
Each timestamp is a number representing the number of seconds since 1970-01-01 00:00:00 UTC. This is not the most convenient means of
expressing date ranges, but until notmuch is fixed to accept a more convenient form, one can use the date program to construct timestamps.
For example, with the bash shell the following syntax would specify a date range to return messages from 2009-10-01 until the current time:
$(date +%s -d 2009-10-01)..$(date +%s)
SEE ALSO notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5), notmuch-new(1), notmuch-reply(1), notmuch-restore(1),
notmuch-search(1), notmuch-show(1), notmuch-tag(1)Notmuch 0.13.2 2012-06-01 NOTMUCH-SEARCH-TERMS(7)