zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: Parse apache error_log
Date: Fri, 1 May 2015 10:33:46 -0700	[thread overview]
Message-ID: <150501103346.ZM3354@torch.brasslantern.com> (raw)
In-Reply-To: <XnsA48DA9D8816E2davidrayninfocouk@80.91.229.13>

On May 1,  3:41pm, zzapper wrote:
} Subject: Parse apache error_log
}
} Hi
} Don't know if this is a job for zsh or sed etc

I'd probably do it in perl because you need to both parse the text and
build up a data structure of results grouped by one of the fields.

} Format:-
} [Fri May 01 16:25:05 2015] [error] [client 172.18.158.61] PHP Parse error:  
} syntax error, unexpected T_VARIABLE 
} 
} I want to grab the date-time of the last entry and then display all the 
} entries with the same date-time.

The approach I would take is to create a hash keyed on the date string
with each value an array of error messages.  As each line is parsed,
push it onto the array for the date key.  You can't easily do that
in zsh (though you could just append to a text string).

However, if the file is small enough that it's OK to scan it multiple
times, you can make one pass to find the date string you care about and
then a second pass, probably with fgrep, to extract all the lines that
have that timestamp.

It sort of depends on what you want to do with the results after you have
collected them.  If you're just going to output them, perl may be more
than you need.


  reply	other threads:[~2015-05-01 17:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 15:41 zzapper
2015-05-01 17:33 ` Bart Schaefer [this message]
2015-05-01 21:03 ` Peter Stephenson
2015-05-01 21:50   ` zzapper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=150501103346.ZM3354@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).