supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: Pattern matching to different logfiles
Date: Tue, 3 Jan 2006 15:11:49 +0100	[thread overview]
Message-ID: <20060103141149.10113.qmail@4c728d979d4855.315fe32.mid.smarden.org> (raw)
In-Reply-To: <92344711-E374-4C12-BC7E-5D71D5491B96@nednieuws.com>

On Tue, Dec 20, 2005 at 01:47:45PM +0100, Charles M. Gerungan wrote:
> I have a log that I would like to split to different files. Every  
> line is prepended with a keyword and I'd like to output to a logdir  
> named keyword. So if there are 5 different keywords I'd like to log  
> to five different logdirs, if possible deleting that keyword  
> (including the trailing space) from the line in the process. Is that  
> possible?

Yes.  Stripping the keyword from the log messages must be done through a
processor though I think, see svlogd(8).

Regards, Gerrit.


      reply	other threads:[~2006-01-03 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 12:47 Charles M. Gerungan
2006-01-03 14:11 ` Gerrit Pape [this message]

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=20060103141149.10113.qmail@4c728d979d4855.315fe32.mid.smarden.org \
    --to=pape@smarden.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.
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).