X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C869A1.C3F6E0E0@onstor-exch02.onstor.net>; Thu, 7 Feb 2008 08:54:47 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: 21717
Date: Thu, 7 Feb 2008 08:54:47 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08265809@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03B1C040@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 21717
Thread-Index: AchpLUHyNxFqfpiITGurkpGx/MSMJgAAE6QwABz7N2A=
References: <20080206180047.494f28d3@ripper.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E03B1C040@onstor-exch02.onstor.net>
From: "John Keiffer" <john.keiffer@onstor.com>
To: "Rendell Fong" <rendell.fong@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>


This stuff is mostly over my head (as you both probably already know).

These are the lines in my Bobcat Cougar system's crontab:

MAILTO=3D""
SHELL=3D/bin/sh
PATH=3D/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/agile/bin:/onstor/bin
HOME=3D/var/log

Those lines are not in the Cougar systems. Are you suggesting we add the
MAILTO line?

Thanks,
John

-----Original Message-----
From: Rendell Fong=20
Sent: Wednesday, February 06, 2008 6:13 PM
To: Andy Sharp; John Keiffer
Subject: RE: 21717

I've seen situations where emrscron (launched via crontab) indirectly
causes emails to be generated when an error occurs while running an
nfxsh or sh cmd.  Will setting MAILTO in the crontab suppress emails
from getting generated this way?  I hope so because it will be a while
before we can be sure that support.sh and emrscron are fixed for Cougar.

Rendell


-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, February 06, 2008 6:01 PM
To: John Keiffer
Cc: Rendell Fong
Subject: Re: 21717

Hmm, there is a separate bug that is involved here, one that can also
lead to "queue full" and /var filling up, albeit after a very long time.

For some reason, we aren't getting the line

MAILTO=3D""

at the top of the root crontab.  That can be added by hand until we get
it straightened out, probably in the next submittal.  Feel free to file
a new bug report on that.

Cheers,

a


On Wed, 6 Feb 2008 12:26:18 -0800 "John Keiffer"
<john.keiffer@onstor.com> wrote:

> I checked the frozen messages on 2 different systems and I found that
> they have different errors. So the question is where this
> configuration lives, so that I we can try and edit it.
>=20
> =20
>=20
> g10r10:~# cat /var/spool/exim4/msglog/1JMqhe-0001BV-5h
>=20
> 2008-02-06 12:17:06 Received from root@ U=3Droot P=3Dlocal S=3D785
>=20
> 2008-02-06 12:17:09 routing failed for root@: mail domain "" is
> syntactically invalid
>=20
> Process failed (1) when writing error message to root@ (frozen)
>=20
> =20
>=20
> g6r10:~# cat /var/spool/exim4/msglog/1JMqks-0003I1-U6
>=20
> 2008-02-06 12:20:27 Received from <> R=3D1JMqiY-000340-EW =
U=3DDebian-exim
> P=3Dlocal S=3D4260
>=20
> 2008-02-06 12:20:27 routing failed for root@g6r10: Unrouteable address
>=20
> *** Frozen (delivery error message)
>=20
> =20
>=20
> Thank you,
>=20
> John Keiffer
>=20
> =20
>=20
> =20
>=20
