X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: Cron jobs visible Date: Mon, 10 Aug 2009 14:15:02 +0200 Lines: 21 Message-ID: References: <20090810113424 DOT GL3204 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/2.9.5 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com * Corinna Vinschen (Mon, 10 Aug 2009 13:34:25 +0200) > On Aug 10 12:57, Thorsten Kampe wrote: > > I upgraded to Windows 7 on Sunday and now whenever cron runs a job, > > the new forked cron process is visible in a console window. I > > suspect that this might be related to the new "Console Window Host" > > (conhost.exe) as I also get this window when I run screen inside a > > shell. > > Cygwin 1.5.25, I presume. Cygwin 1.5.25 is not supported under W7. Use > Cygwin 1.7 instead. It contains workarounds for a few really incredible > bugs introduced in Windows 7 in terms of console windows. I reported two > of them in the beta testing phase. One of them has been only partially > fixed (and introduced a new one in the W7 32 bit), the other one hasn't > been fixed at all in RTM. Thanks for the insight and background information. I'll probably wait until 1.7 is out of beta and an "official" migration document is released. But maybe the annoyance factor becomes too high and I'll do that even sooner. Thanks again, Thorsten -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple