RE: Log filtering

2002-11-02 Thread Furnish, Trever G
Probably a dead thread by now, but you should also check the logwatch package, which is probably already installed for you and running nightly.  You ARE checking the mail sent to the root account, right?   Logwatch allows you to write your own little scripts (such as the grep statements other

Re: Log filtering

2002-10-14 Thread Rudolf Amirjanyan
Thanks Joseph. Everything is working fine. I was wrong, It is doing just what I need. Thank you very mach. - Original Message - From: "Rudolf Amirjanyan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 15, 2002 6:10 AM Subject: Re: Log filtering

Re: Log filtering

2002-10-14 Thread Michael Fratoni
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 14 October 2002 08:14 pm, Craig Iffelberg wrote: > Ok then what would I type to get rid of all the > > cmd.exe rubbish in my access_log file. > > What I typed was: > > grep -v cmd.exe access_log Unless you redirect the output, this will jus

Re: Log filtering

2002-10-14 Thread Rudolf Amirjanyan
I'm sorry, but it has done something else. - Original Message - From: "Joseph V Moss" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 15, 2002 5:46 AM Subject: Re: Log filtering > > Assuming that is actually stored in the file as

Re: Log filtering

2002-10-14 Thread Frank Bax
grep -v ^b$ myfile > newfile At 06:43 PM 10/14/02, Rudolf Amirjanyan wrote: >I have a file like this > >a >b >a >b > >How I can filter this file, so that all the lines containing >b, were deleted. >Is there any way to do

Re: Log filtering

2002-10-14 Thread Joseph V Moss
3:46.330 UTC Sat Oct 5 2002, DisconnectTime > 15:43:46.330 UTC Sat Oct 5 2002 > > > > Thanks > > > From: "Joseph V Moss" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, October 15, 2002 3:56 AM > Subject: Re: Lo

Re: Log filtering

2002-10-14 Thread Craig Iffelberg
Ok then what would I type to get rid of all the cmd.exe rubbish in my access_log file. What I typed was: grep -v cmd.exe access_log then sed /cmd.exe/ d' access_log then awk '/cmd.exe/ {next} {print} access_log My version of what I wanted it to do. On Monday 14 October 2002 07:11 pm,

Re: Log filtering

2002-10-14 Thread Samuel Flory
Craig Iffelberg wrote: >Hey why wont it work for me? > >I typed in exactly what was in the e mail and >it said > > >sed: -e expression #1, char 8: Missing command > > You can't of typed in exactly the what was in the email. The expression was 15 char long!!! What the above says is "the t

Re: Log filtering

2002-10-14 Thread Rudolf Amirjanyan
I need only this fields: 091422594759#, ConnectTime 15:43:46.330 UTC Sat Oct 5 2002, DisconnectTime 15:43:46.330 UTC Sat Oct 5 2002 Thanks From: "Joseph V Moss" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 15, 2002 3:56 AM Subject: Re: Log filteri

Re: Log filtering

2002-10-14 Thread Craig Iffelberg
Hey why wont it work for me? I typed in exactly what was in the e mail and it said sed: -e expression #1, char 8: Missing command On Monday 14 October 2002 05:56 pm, Joseph V Moss wrote: > > I have a file like this > > > > a > > b > > a > > b >

Re: Log filtering

2002-10-14 Thread Rudolf Amirjanyan
Thanks a lot. "sed" works perfectly :)) - Original Message - From: "Joseph V Moss" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 15, 2002 3:56 AM Subject: Re: Log filtering > > I have a file like this > > > >

Re: Log filtering

2002-10-14 Thread Joseph V Moss
> I have a file like this > > a > b > a > b > > How I can filter this file, so that all the lines containing b, were >deleted. > Is there any way to do it ? > Thanks in advance. > There are *lots* of ways to do it. Here are just th