From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21251 invoked by alias); 4 Nov 2003 05:21:19 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 21244 invoked from network); 4 Nov 2003 05:21:18 -0000 Received: from unknown (HELO fed1mtao08.cox.net) (68.6.19.123) by sources.redhat.com with SMTP; 4 Nov 2003 05:21:18 -0000 Received: from cox.net ([68.105.193.68]) by fed1mtao08.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031104052116.GRTV720.fed1mtao08.cox.net@cox.net> for ; Tue, 4 Nov 2003 00:21:16 -0500 Message-ID: <3FA73747.3DF859E2@cox.net> Date: Tue, 04 Nov 2003 05:21:00 -0000 From: Sponge Bob X-Accept-Language: en MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Clean installed and Bash marked "not executable" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2003-11/txt/msg00125.txt.bz2 I did a clean install of the latest cygwin and for some bizarre reason /usr/bash(.exe) is marked "not executable" after the installation. This causes a problem with openssh because when an incoming session comes it tries to run bash and finds it "not executable" and will reject the login with a cryptic message. Only by turning on debug mode for sshd in the windows registry and looking at the sshd log did I finally figure out it was the bash "not executable" problem. -- 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/