X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 5 Jun 2008 19:32:36 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Patch to allow Cron to use non-POSIX shells like Powershell.exe and CMD.exe Message-ID: <20080605233236.GA29771@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <2abc9c2d0806040808s2178885ak5dcf7cd528ea685a AT mail DOT gmail DOT com> <2abc9c2d0806040948l2f6dc1cbjd99bbdaea65cf181 AT mail DOT gmail DOT com> <006701c8c756$1b923260$d50410ac AT wirelessworld DOT airvananet DOT com> <2abc9c2d0806051528w6aa5c8f5g6bf946291171d579 AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Thu, Jun 05, 2008 at 06:43:25PM -0400, Mark J. Reed wrote: >The sh process is not "extra" since it's replaced by the powershell >process, right? Unless "exec" works differently in Cygwin, which is >entirely possible.... Nope, you're right. It is replaced as long as it isn't the top-level cygwin process. There still is going to be neglible overhead from running a shell to start a shell but, since this isn't an interactive process, it is hard to see why that would matter. Obligatory free software inspirational observation: Using the available tools to solve the problem seems like a winning way of doing this to me but the power of free software is that we don't have to dictate how things are done. If the OP wants to maintain his own patch (as he does) then he has the power to do just that. cgf -- 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/