Trevor,
this wrapping is done by design and could not be changed! Any log line,
that contains a filename after a '->' , will be wrapped after this
possition.
How ever, if you do not want to see filenames, just use the search pattern
-.eml . The (-) in front of a word will search for lines which does
not contain it.
The search engine is realy intelligent. You may use any combination of
words with or without a ( - ) in front.
for example : [email protected] [spam found] -discarded -newsletter
This example is like an extended BlockReport. It searches for all log
lines for the address where spam was found but not discarded and the
subject not contains 'newsletter' .
Thomas
Trevor Jacques <[email protected]>
20.10.2009 14:36
Bitte antworten an
ASSP development mailing list <[email protected]>
An
ASSP development mailing list <[email protected]>
Kopie
Thema
Re: [Assp-test] Antwort: Re: fixes and changes in 2.0.1_RC0.5.01
> <[email protected]> wrote:
>>> BTW, I suspect you missed/forgot the wrap at: field. Something for the
next update. :-)
>> Where do you want to wrap a log line - at possion 1000 ?? :)
:-)
Sometimes, yes, because that's not the way I look at it. It does/should
not matter what value the user would want. The lines should simply be
lines, and the user gets to set where they wrap (notwithstanding the
default setting of, say, 80).
For example, if I'm looking for something in the logs, it is often useful
to look for visual patterns on the text. Those visual patterns are greatly
broken up by line with line feeds in them, so I want no line feeds to
muddle the visual.
Hence, we need to assume that all log 'lines' are on a single line and
work from there to, say, 80 characters for presentation. That way the user
is the one who determines whether ANY line feeds occur in the report.
Making an a priori decision that 'nobody would want more than x
characters' and make the internal workings use that value is not the way
to go (again, notwithstanding that it is certainly reasonable to set the
default presentation value to 80).
I noticed that there are still errant line feeds in the report (you may
already be working on these). The line length was set to 2,500 for the
report that created these:
Oct-20-09 08:07:07 id-40418-10668 [Worker_1] [Whitelisted] 209.196.3.80
<[email protected]> to: [email protected] whitelisted
(no bad attachments) [Re Multi file uploaderDoes the destination of the
file have to be running lasso or can it be] ->
./notspam/Re_Multi_file_uploaderDoes_the_destination_of_the_--42710.eml
Oct-20-09 08:07:07 id-40418-10668 [Worker_1] [MessageOK] 209.196.3.80
<[email protected]> to: [email protected] message ok [Re
Multi file uploader] ->
./notspam/Re_Multi_file_uploaderDoes_the_destination_of_the_--42710.eml
Oct-20-09 08:15:09 id-40907-07736 [Worker_4] [Collect] 114.143.34.156
<[email protected]> to: [email protected] [spam found]
(Collect Address: [email protected]) [With a stylish watch you can
impress anyone you want] ->
./discarded/With_a_stylish_watch_you_can_impress_anyone_you_wa--42711.eml;
Oct-20-09 08:15:20 id-40907-04011 [Worker_5] [Whitelisted] 209.196.3.80
<[email protected]> to: [email protected] whitelisted
(no bad attachments) [Re Multi file uploader 0AThe process uses Lasso yes
however you can alter the tag to use ftp put] ->
./notspam/Re_Multi_file_uploader_0AThe_process_uses_Lasso_ye--42712.eml
Oct-20-09 08:15:20 id-40907-04011 [Worker_5] [MessageOK] 209.196.3.80
<[email protected]> to: [email protected] message ok [Re
Multi file uploader] ->
./notspam/Re_Multi_file_uploader_0AThe_process_uses_Lasso_ye--42712.eml
Oct-20-09 08:17:53 id-41045-00047 [Worker_7] [Collect] 217.219.161.193
<[email protected]> to: [email protected] [spam found] (Collect
Address: [email protected]) [admiral s limited edition] ->
./discarded/admiral_s_limited_edition--42713.eml;
T.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
