www.delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Message-Id: | <200207051920.g65JKbE87216@pilot16.cl.msu.edu> |
Date: | Fri, 05 Jul 2002 15:20:36 EDT |
To: | cygwin AT cygwin DOT com |
Subject: | Re: OpenSSH-3.4p1-2 bug in ssh-host-config |
From: | Harold L Hunt <huntharo AT msu DOT edu> |
Marc, > [beej AT beej-lap]~:{506}:$ ls //etc/ssh* > ls: //etc/ssh*: No such file or directory > [beej AT beej-lap]~:{507}:$ ls /etc/ssh* > /etc/ssh_config Here is one more interesting bit: hunt AT NUCFAC13 ~ $ ls /etc//ssh* /etc//sshd_config So, an extra / somewhere in the middle of the path doesn't cause problems, but an extra leading / does cause problems. Both 'ls //etc/ssh*' and 'ls /etc//ssh*' work under bash on Linux (so this isn't a bash problem in general). Maybe this is a Windows command prompt escape problem (I didn't think that / was special to the Windows command prompt, but I could be mistaken)? Harold -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |