X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C869AF.0EB013B4@onstor-exch02.onstor.net>; Thu, 7 Feb 2008 10:29:56 -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 10:29:55 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E083506B5@onstor-exch02.onstor.net>
In-Reply-To: <20080207091237.4c9393c7@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 21717
Thread-Index: AchprKUKsuXFUnSaRSy3tYpr12cBDwAAj79A
References: <20080206180047.494f28d3@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E03B1C040@onstor-exch02.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E08265809@onstor-exch02.onstor.net> <20080207091237.4c9393c7@ripper.onstor.net>
From: "John Keiffer" <john.keiffer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Rendell Fong" <rendell.fong@onstor.com>

Okay, I added the following lines to the crontab on my Cougar since they
were all missing:

MAILTO=3D""
HOME=3D/var/log
#
#minute hour    mday    month   wday    command

Do I just leave the mailto blank?

Thanks,
John

-----Original Message-----
From: Andy Sharp=20
Sent: Thursday, February 07, 2008 9:13 AM
To: John Keiffer
Cc: Rendell Fong
Subject: Re: 21717

On Thu, 7 Feb 2008 07:54:47 -0800 "John Keiffer"
<john.keiffer@onstor.com> wrote:

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

I don't know, it sounds like you got it pretty much exactly.

> These are the lines in my Bobcat Cougar system's crontab:
>=20
> MAILTO=3D""
> SHELL=3D/bin/sh
> PATH=3D/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/agile/bin:/onstor/bin
> HOME=3D/var/log
>=20
> Those lines are not in the Cougar systems. Are you suggesting we add
> the MAILTO line?

Add the MAILTO and HOME lines.  The others aren't necessary on Linux.
=20
> Thanks,
> John
>=20
> -----Original Message-----
> From: Rendell Fong=20
> Sent: Wednesday, February 06, 2008 6:13 PM
> To: Andy Sharp; John Keiffer
> Subject: RE: 21717
>=20
> 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.
>=20
> Rendell
>=20
>=20
> -----Original Message-----
> From: Andy Sharp=20
> Sent: Wednesday, February 06, 2008 6:01 PM
> To: John Keiffer
> Cc: Rendell Fong
> Subject: Re: 21717
>=20
> 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.
>=20
> For some reason, we aren't getting the line
>=20
> MAILTO=3D""
>=20
> 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.
>=20
> Cheers,
>=20
> a
>=20
>=20
> On Wed, 6 Feb 2008 12:26:18 -0800 "John Keiffer"
> <john.keiffer@onstor.com> wrote:
>=20
> > 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
