cronjob and logcheck
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
Signature · 1 line
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5
Quoted 5 lines · Ulrich Wiederhold
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".
Quoted 4 lines
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.
Quoted 4 lines
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?
Quoted 13 lines
Thanks.
UliSignature · 7 lines
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5 _______________________________________________ linux-lvm mailing list [email protected] http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
Signature · 15 lines
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
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Hello,
Quoted 7 lines · Heinz J . Mauelshagen
Quoted 3 lines · Ulrich Wiederhold
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.
Quoted 2 lines
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
Signature · 1 line
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5
Quoted 7 lines · Ulrich Wiederhold
Hello,
Quoted 5 lines · Heinz J . Mauelshagen
Quoted 3 lines · Ulrich Wiederhold
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)
Quoted 5 lines
Quoted 2 lines
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.
Quoted 6 lines
Quoted 3 lines
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.
Quoted 11 lines
Uli
Signature · 7 lines
'The box said, 'Requires Windows 95 or better', so i installed Linux - TKK 5 _______________________________________________ linux-lvm mailing list [email protected] http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
Signature · 15 lines
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
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Quoted 1 line · Heinz J . Mauelshagen
On Tue, Feb 12, 2002 at 04:27:44PM +0100, Ulrich Wiederhold wrote:
<snip>
Quoted 6 lines
Quoted 3 lines
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
Signature · 2 lines
Andreas Piesk [email protected] PGP-Fingerprint: 23CB A7E2 2E53 373C DBCD 8EFC 7777 61C1