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: Wed, 4 Jun 2003 16:48:29 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Slight patch for Cron Message-ID: <20030604144829.GU875@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030603183428.GM875@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Jun 04, 2003 at 09:53:05AM +0200, Ronald Landheer-Cieslak wrote: > On Tue, 3 Jun 2003, Corinna Vinschen wrote: > > Does it help to set CYGWIN=notty before starting cron? > Apparently not, no. > > Because I'm starting cron from the "startup" part of the start menu, I had > to run it from a batch file ( > set CYGWIN=notty > cron.exe > ) but I don't think that should make a difference. Could you just for fun add a call to RegisterServiceProcess() (that works on 9x/Me only) right before the setsid() call in the child code and try again? 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/