Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 4 Jul 2002 16:09:03 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: cygwin-1.3.12-1 Message-ID: <20020704200903.GA7739@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20020704190451 DOT E21857 AT cygbert DOT vinschen DOT de> <20020704215212 DOT G21857 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020704215212.G21857@cygbert.vinschen.de> User-Agent: Mutt/1.3.23.1i On Thu, Jul 04, 2002 at 09:52:12PM +0200, Corinna Vinschen wrote: >On Thu, Jul 04, 2002 at 07:56:48PM +0100, Tony Arnold wrote: >> Corrinna, > >Almost... > >> On Thu, 4 Jul 2002, Corinna Vinschen wrote: >> My reading of it is that the passwd file is read, but HOME is not set >> because it thinks it is already set! > >Looks like a bug in Cygwin which happens on changing user context. FWIW, running strace from a cron job isn't necessarily going to do the right thing. strace introduces a barrier between information presented by crond and (in this case) /bin/echo. It makes /bin/echo think it's running in a raw windows environment rather than a cygwin environment. It might be more interesting to run strace on cron itself (if that's even possible) and then inspect the results. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/