Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "linda w \(cyg\)" <cygwin AT tlinx DOT org>
To: <cygwin AT cygwin DOT com>
Subject: getting cron to work -> status too large for sendmail?
Date: Tue, 27 May 2003 11:54:49 -0700
Message-ID: <000701c32481$733db1b0$1403a8c0@sc.tlinx.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal


I was trying to get cron to work -- it looks like it is
invoking something on a regular basis, however, it is also
trying to send the 1 line of output of cron job to the owner.

In the process it includes the entire environment (in this case
of the user who started cron, me). It includes the environment
as Header lines:
X-Cron-Env: <SESSIONNAME=Console>
X-Cron-Env: <SHLVL=1>
...[78 more lines of Environment Variable listing]

This causes sendmail to fail since apparently sendmail has a 4000
character limit in the header.

I don't know that I've seen cron include the entire environment
as header lines before.  Is that normal behavior?

Am I just exceptionally 'lucky' in that I've hit an obscure limit
in sendmail or is this a limitation of sendmail on cygwin?

Any ideas where I should start to address this would be appreciated.
It seems slightly kludgey to, say write a manual script to clear 
out the environment, but I dunno -- no more kludgy than hard 
coding a 4000 character header limit...

-linda


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/