==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this
link:http://bugs.contribs.org/show_bug.cgi?id=8536
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
Bug ID: 8536
Summary: cron job too verbose
Classification: Contribs
Product: SME Contribs
Version: 9beta
Hardware: ---
OS: ---
Status: CONFIRMED
Severity: normal
Priority: P3
Component: smeserver-bandwidthd
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
every week a cron job run to update mysql table in order to reduce their size.
However we do not need to know that the table is already up to date or that the
status is ok after optimization .
I suggest changing the cron job from
/bin/sh /usr/share/doc/bandwidthd-2.0.1.1/phphtdocs/bd_mysql_purge.sh |mysql
`/sbin/e-smith/db configuration getprop bandwidthd DbName`
to
/bin/sh /usr/share/doc/bandwidthd-2.0.1.1/phphtdocs/bd_mysql_purge.sh |mysql
`/sbin/e-smith/db configuration getprop bandwidthd DbName`|grep -v 'Msg_type'|
grep -v 'Table is already up to date'|grep -v 'status OK'
this way we only get a cron message when there is a corrupted table and we need
to do something.
alternatively, I could just remove the "already up to date" lines in order to
keep info on optimized tables....
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/
