From: "Michael J. Forster" <mike@sharedlogic.ca>
Subject: Re: Socklog feature request
Date: Sun, 8 Aug 2004 11:00:44 -0700 [thread overview]
Message-ID: <20040808180044.GB77867@sartre.sharedlogic.ca> (raw)
In-Reply-To: <20040808170954.26356.qmail@470640bb66f618.315fe32.mid.smarden.org>
On Sun, Aug 08, 2004 at 05:09:53PM +0000, Gerrit Pape wrote:
> On Sun, Aug 08, 2004 at 04:28:35PM +0200, Alexander Lazic wrote:
> > On Son 08.08.2004 11:22, Gerrit Pape wrote:
> > >http://marc.theaimsgroup.com/?t=104379616100007&r=1&w=2
> > >http://marc.theaimsgroup.com/?t=104064482600002&r=1&w=2
> > Thanx for the links ;-)
>
> > >>I need to rotate the logs per day but haven't found a easy way to do
> > >>this with socklog.
> > >Why do you need? I would advise to make use of the great feature of
>
> > The filesize is not my problem. When i look into the file of e.g Friday
> > then i want _all_ data from Friday are in one logfile, if it is 1GB or
> > whatever it is so.
I suggest separating the notions of log collection and analysis,
as would a database programmer the notions of physical and logical
data structure.
On the servers I manager, file sizes under /var/log are of concern.
I let multilog do its thing and, on a daily (or hourly, as necessary)
basis, I move any rotated logs to a place where space isn't a
concern. From there, some simple shell scripts can extract log
entries by date regardless of the files involved.
-Mike
prev parent reply other threads:[~2004-08-08 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040807084800.GA7779@none.at>
[not found] ` <20040808112240.3636.qmail@678ff29a1e7219.315fe32.mid.smarden.org>
2004-08-08 14:28 ` Alexander Lazic
2004-08-08 17:09 ` Gerrit Pape
2004-08-08 18:00 ` Michael J. Forster [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=20040808180044.GB77867@sartre.sharedlogic.ca \
--to=mike@sharedlogic.ca \
/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).