X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org X-SpamScore: -10 X-BigFish: VPS-10(zd61pz542N1432R1805M9371Pzz1202hzza25fsz2fh6bh61h) X-Spam-TCS-SCL: 0:0 X-FB-SS: 5, From: Bruce Dobrin To: "Thrall, Bryan" , "cygwin AT cygwin DOT com" Date: Wed, 8 Jul 2009 15:23:07 -0700 Subject: RE: identical scripts don't behave identically Message-ID: <5369FDACFFACA04182E47E00D46B71810AD335D904@LAX-EXCH03.spimageworks.com> References: <24400289 DOT post AT talk DOT nabble DOT com> <786EBDA1AC46254B813E200779E7AD361E69CB AT srv1163ex1 DOT flightsafety DOT com> In-Reply-To: <786EBDA1AC46254B813E200779E7AD361E69CB@srv1163ex1.flightsafety.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 I'll bet one has a carriage return ( and/or line feed) and the other doesn'= t which would fail on an incomplete last line. I've been burned by this ma= ny times. Always end the script by hitting the enter to avoid this. -----Original Message----- From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of= Thrall, Bryan Sent: Wednesday, July 08, 2009 3:19 PM To: cygwin AT cygwin DOT com Subject: RE: identical scripts don't behave identically roc97007 wrote on Wednesday, July 08, 2009 5:11 PM: > To summarize, as far as I can tell the files are identical, but one works > and the other can't seem to find the current directory. If, in the broken > script, I substitute any command that needs to read or write to or from the > file system, it will always fail with "file not found" or "no such file or > directory". The other script with the exact same commands (assuming they > are legal and reasonable) will always work. > > Obviously there is a difference between the files. I can't figure out what > it is. The issue is demonstrably a characteristic of the file, because if I > delete or rename aaa.sh and then "cp aab.sh aaa.sh", then they will both > work. > > This is driving me crazy. We are under a deadline, and some scripts work > and some do not, seemingly randomly. Our current work-around is to copy a > script that works to a different name and then replace the content. This is > a ridiculous workaround, and since we don't know what the mechanism is we > have no idea if it'll still work tomorrow or next week. > > Please help! Perhaps one of the files has DOS line endings and the other has UNIX line endings? Try d2u on the broken one to see if it fixes the problem. -- Bryan Thrall FlightSafety International bryan DOT thrall AT flightsafety DOT com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple