Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-21 Thread Justin Pryzby
On Mon, Apr 21, 2008 at 08:43:22AM +0200, Marc Haber wrote: > On Sun, Apr 20, 2008 at 09:30:33PM -0400, Justin Pryzby wrote: > > I rewrote your patch to use a tempfile instead to reduce code > > duplication. > > I'd rather have a few megs of code grepped twice than using a tempfile. I don't know i

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-20 Thread Marc Haber
On Sun, Apr 20, 2008 at 09:30:33PM -0400, Justin Pryzby wrote: > I rewrote your patch to use a tempfile instead to reduce code > duplication. I'd rather have a few megs of code grepped twice than using a tempfile. Greetings Marc -- ---

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-20 Thread Justin Pryzby
On Sun, Apr 20, 2008 at 10:41:10PM +0200, Marc Haber wrote: > On Sun, Apr 20, 2008 at 04:21:38PM -0400, Justin Pryzby wrote: > > On Sun, Apr 20, 2008 at 09:34:04PM +0200, Marc Haber wrote: > > > On Thu, Apr 17, 2008 at 08:41:52AM -0400, Justin Pryzby wrote: > > > > That's probably due to very low m

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-20 Thread Marc Haber
On Sun, Apr 20, 2008 at 04:21:38PM -0400, Justin Pryzby wrote: > On Sun, Apr 20, 2008 at 09:34:04PM +0200, Marc Haber wrote: > > On Thu, Apr 17, 2008 at 08:41:52AM -0400, Justin Pryzby wrote: > > > That's probably due to very low mail volume on this laptop machine, in > > > combination with an earl

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-20 Thread Justin Pryzby
On Sun, Apr 20, 2008 at 09:34:04PM +0200, Marc Haber wrote: > On Thu, Apr 17, 2008 at 08:41:52AM -0400, Justin Pryzby wrote: > > That's probably due to very low mail volume on this laptop machine, in > > combination with an earlier logfile rotation. > > Please try the following patch against the d

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-20 Thread Marc Haber
On Thu, Apr 17, 2008 at 08:41:52AM -0400, Justin Pryzby wrote: > That's probably due to very low mail volume on this laptop machine, in > combination with an earlier logfile rotation. Please try the following patch against the daily cron job: --- debian/exim4-base.cron.daily(revision 2260

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-18 Thread Andreas Metzler
On 2008-04-17 Justin Pryzby <[EMAIL PROTECTED]> wrote: [...] > /var/log/exim4/mainlog > 2008-04-17 07:42:11 Start queue run: pid=12298 > 2008-04-17 07:42:11 End queue run: pid=12298 > 2008-04-17 08:12:10 Start queue run: pid=12583 > 2008-04-17 08:12:10 End queue run: pid=12583 > 2008-04-17 08:30:32

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-17 Thread Marc Haber
On Thu, Apr 17, 2008 at 08:41:52AM -0400, Justin Pryzby wrote: > On Wed, Apr 16, 2008 at 07:41:44AM -0400, Anacron wrote: > > /etc/cron.daily/exim4-base: > > No valid log lines read > > Null message body; hope that's ok > > That's probably due to very low mail volume on this laptop machine, i

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-17 Thread Justin Pryzby
On Fri, Apr 18, 2008 at 12:04:41AM +0200, Marc Haber wrote: > And you have E4BCD_DAILY_REPORT set to non-empty? Yes -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#476541: exim4-base: please handle nearly-empty logfile in daily cronjob stats

2008-04-17 Thread Justin Pryzby
Package: exim4-base Version: 4.69-2+b1 File: /etc/cron.daily/exim4-base Sometimes, I get these messages rather than the expected report (The first message is empty): On Wed, Apr 16, 2008 at 07:35:09AM -0400, root wrote: On Wed, Apr 16, 2008 at 07:41:44AM -0400, Anacron wrote: > /etc/cron.daily/e