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, 16 Jun 2004 09:32:04 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Running ssh from procmail Message-ID: <20040616073204.GA1365@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <004b01c44fe3$68ff0350$ac050b0a@PWISNOVSKY> <007601c4526b$02aff200$ac050b0a@PWISNOVSKY> <20040615083401.GD15387@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.2i On Jun 15 20:02, Peter Wisnovsky wrote: > No such luck...moreover wouldn't a missing binary or dll lead to a link > or exec failure? Not in this case since the WinSock DLL is loaded dynamically at runtime. The error messages seem to indicate that the child process couldn't find the WinSock DLL anymore. I'm really surprised that adding the standard Windows paths doesn't help here. Could you start ssh with -vvv optin and see if that gives us a hint? Corinna > > Peter > > On Jun 15, 2004, at 1:34 AM, Corinna Vinschen wrote: > >Add the usual Windows paths to $PATH, e.g. on my system that would be > > > > > >PATH=/bin:/usr/bin:/pkg/mail/bin:/cygdrive/c/WINDOWS/system32:/ > >cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem > > > >Then try your original solution again. I have this feeling it will > >help. -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader 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/