Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 11 Aug 2003 18:08:37 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Problem with cron! Message-ID: <20030811160836.GL3101@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200308110911.h7B9BVXt019765@no14.dca1.superb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Mon, Aug 11, 2003 at 11:20:25AM -0400, Igor Pechtchanski wrote: > On Mon, 11 Aug 2003 cygwin at harrier dot ch wrote: > > [unnecessary full quote deleted, grrrrr] > > I've just compared cron-3.0.1-9 and > cron-3.0.1-10, and the only difference was that the stdin and stdout > streams were redirected from/to /dev/null. You might try to use the > executable from cron-3.0.1-9, just to minimize the search space. If it > works, you know the latest change was the culprit. If it doesn't, the > culprit is in something that changed between -8 and -9. FWIW, the changes -9 introduced a change explicitely for 9x which results in the full environment not being propagated to child processes. The discussion should be in the cygwin ML archive. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/