All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] cronjob and logcheck
@ 2002-02-12  9:24 Ulrich Wiederhold
  2002-02-12  9:43 ` Heinz J . Mauelshagen
  0 siblings, 1 reply; 5+ messages in thread
From: Ulrich Wiederhold @ 2002-02-12  9:24 UTC (permalink / raw)
  To: linux-lvm

Hi,
I have 2 questions:

1. What for is this cron-job?
*/10 *  * * *   root    /sbin/lvmsadc > /var/log/lvm >/dev/null 2>&1

2. I use logcheck and these msg are annoying:
Feb 12 14:20:01 home /USR/SBIN/CRON[28697]: (root) CMD (/sbin/lvmsadc >
/var/log/lvm >/dev/null 2>&1)

Why don't you create some logcheck "information" files in a next
lvm-version, that display the really important msg and ignore the usual
ones?


Thanks.
Uli

-- 
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [linux-lvm] cronjob and logcheck
  2002-02-12  9:24 [linux-lvm] cronjob and logcheck Ulrich Wiederhold
@ 2002-02-12  9:43 ` Heinz J . Mauelshagen
  2002-02-12 11:09   ` Ulrich Wiederhold
  2002-02-12 12:06   ` Re[2]: " Andreas Piesk
  0 siblings, 2 replies; 5+ messages in thread
From: Heinz J . Mauelshagen @ 2002-02-12  9:43 UTC (permalink / raw)
  To: linux-lvm

On Tue, Feb 12, 2002 at 04:27:44PM +0100, Ulrich Wiederhold wrote:
> Hi,
> I have 2 questions:
> 
> 1. What for is this cron-job?
> */10 *  * * *   root    /sbin/lvmsadc > /var/log/lvm >/dev/null 2>&1

It does io statistics samples on all your logical volumes which
can be retrieved by "lvmsar /var/log/lvm".

> 
> 2. I use logcheck and these msg are annoying:
> Feb 12 14:20:01 home /USR/SBIN/CRON[28697]: (root) CMD (/sbin/lvmsadc >
> /var/log/lvm >/dev/null 2>&1)

Because the cron entry doesn't create any STDOUT/STDERR anyway,
that shouldn't happen.

> 
> Why don't you create some logcheck "information" files in a next
> lvm-version, that display the really important msg and ignore the usual
> ones?

Why don't you deactivate the cron entry for lvmsadc until you really
want logical volume io statistics?

> 
> 
> Thanks.
> Uli
> 
> -- 
> 'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [linux-lvm] cronjob and logcheck
  2002-02-12  9:43 ` Heinz J . Mauelshagen
@ 2002-02-12 11:09   ` Ulrich Wiederhold
  2002-02-12 11:35     ` Heinz J . Mauelshagen
  2002-02-12 12:06   ` Re[2]: " Andreas Piesk
  1 sibling, 1 reply; 5+ messages in thread
From: Ulrich Wiederhold @ 2002-02-12 11:09 UTC (permalink / raw)
  To: linux-lvm

Hello,
* Heinz J . Mauelshagen <mauelshagen@sistina.com> [020212 16:42]:
> On Tue, Feb 12, 2002 at 04:27:44PM +0100, Ulrich Wiederhold wrote:
> > 2. I use logcheck and these msg are annoying:
> > Feb 12 14:20:01 home /USR/SBIN/CRON[28697]: (root) CMD (/sbin/lvmsadc >
> > /var/log/lvm >/dev/null 2>&1)
> 
> Because the cron entry doesn't create any STDOUT/STDERR anyway,
> that shouldn't happen.

What's the problem? The file exists but has no contents. I don't get
any other errors.

> Why don't you deactivate the cron entry for lvmsadc until you really
> want logical volume io statistics?

That's a way I could do it, but I would like to know what cause this
problem.

Uli

-- 
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [linux-lvm] cronjob and logcheck
  2002-02-12 11:09   ` Ulrich Wiederhold
@ 2002-02-12 11:35     ` Heinz J . Mauelshagen
  0 siblings, 0 replies; 5+ messages in thread
From: Heinz J . Mauelshagen @ 2002-02-12 11:35 UTC (permalink / raw)
  To: linux-lvm

On Tue, Feb 12, 2002 at 06:13:13PM +0100, Ulrich Wiederhold wrote:
> Hello,
> * Heinz J . Mauelshagen <mauelshagen@sistina.com> [020212 16:42]:
> > On Tue, Feb 12, 2002 at 04:27:44PM +0100, Ulrich Wiederhold wrote:
> > > 2. I use logcheck and these msg are annoying:
> > > Feb 12 14:20:01 home /USR/SBIN/CRON[28697]: (root) CMD (/sbin/lvmsadc >
> > > /var/log/lvm >/dev/null 2>&1)
> > 
> > Because the cron entry doesn't create any STDOUT/STDERR anyway,
> > that shouldn't happen.
> 
> What's the problem? The file exists but has no contents. I don't get
> any other errors.

Well, AFAIU logcheck checks root mails and reports, but there shouldn't
be any mail because of no output of the lvmsadc job.

> 
> > Why don't you deactivate the cron entry for lvmsadc until you really
> > want logical volume io statistics?
> 
> That's a way I could do it, but I would like to know what cause this
> problem.

It is rather a cron problem than an LVM one.

> 
> Uli
> 
> -- 
> 'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re[2]: [linux-lvm] cronjob and logcheck
  2002-02-12  9:43 ` Heinz J . Mauelshagen
  2002-02-12 11:09   ` Ulrich Wiederhold
@ 2002-02-12 12:06   ` Andreas Piesk
  1 sibling, 0 replies; 5+ messages in thread
From: Andreas Piesk @ 2002-02-12 12:06 UTC (permalink / raw)
  To: linux-lvm

Tuesday, February 12, 2002, 4:42:12 PM, Heinz J . Mauelshagen wrote:

> On Tue, Feb 12, 2002 at 04:27:44PM +0100, Ulrich Wiederhold wrote:
<snip>
>> 2. I use logcheck and these msg are annoying:
>> Feb 12 14:20:01 home /USR/SBIN/CRON[28697]: (root) CMD (/sbin/lvmsadc >
>> /var/log/lvm >/dev/null 2>&1)

> Because the cron entry doesn't create any STDOUT/STDERR anyway,
> that shouldn't happen.

well, it SHOULD. this message is generated by cron itself, every time
a job was started. it's cron's normal behaviour.
ulrich, adjust your syslog to get rid of this messages.

ciao -ap

-- 
Andreas Piesk a.piesk@gmx.net
PGP-Fingerprint: 23CB A7E2 2E53 373C  DBCD 8EFC 7777 61C1

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-02-12 12:06 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-02-12  9:24 [linux-lvm] cronjob and logcheck Ulrich Wiederhold
2002-02-12  9:43 ` Heinz J . Mauelshagen
2002-02-12 11:09   ` Ulrich Wiederhold
2002-02-12 11:35     ` Heinz J . Mauelshagen
2002-02-12 12:06   ` Re[2]: " Andreas Piesk

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.