All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] HUGE LVM log file...
Date: Tue, 17 Jul 2001 13:28:59 +0200	[thread overview]
Message-ID: <20010717132859.D17345@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0107171225320.12608-100000@erdos.shef.ac.uk>; from g.liakhovetski@ragingbull.com on Tue, Jul 17, 2001 at 12:28:07PM +0100

On Tue, Jul 17, 2001 at 12:28:07PM +0100, Guennadi Liakhovetski wrote:
> > > My /var/log/lvm has grown up to 800MB+... and has filled up the disk...
> >
> > Remove it.
> > lvmsadc is probably filling it run by cron.
> 
> Thanks! But why / what for is it needed and why is it created by default
> without any size control?

It is not created/activated by default.
Someone must have put it into crontab.

But you are right: there's no size control so far.

> 
> Guennadi
> ___
> 
> Dr. Guennadi V. Liakhovetski
> Department of Applied Mathematics
> University of Sheffield, Sheffield, U.K.
> email: g.liakhovetski@sheffield.ac.uk
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-07-17 11:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 11:13 [linux-lvm] HUGE LVM log file Guennadi Liakhovetski
2001-07-17 11:14 ` Heinz J. Mauelshagen
2001-07-17 11:28   ` Guennadi Liakhovetski
2001-07-17 11:28     ` Heinz J. Mauelshagen [this message]
2001-07-17 21:28     ` Wolfgang Weisselberg
2001-07-18 14:55       ` Heinz J. Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2001-07-17 21:52 Gonyou, Austin
2001-07-18  0:00 ` Wolfgang Weisselberg
2001-07-18  8:22 ` Joe Thornber
2001-07-18  8:48   ` Benoit SERRA
2001-07-18  9:33     ` Joe Thornber
2001-07-18 19:23       ` Ragnar Kjørstad
2001-07-18 22:22         ` lembark
2001-07-18  9:46     ` Adam Cioccarelli
     [not found]     ` <Pine.LNX.4.33.0107181141480.25686-100000@vie-ac.office.ece tra.com>
2001-07-18  9:47       ` Benoit SERRA
2001-07-18 13:29         ` Iain Campbell
2001-07-18 17:02     ` Steven Lembark

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=20010717132859.D17345@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.