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, 6 Mar 2003 15:08:20 -0600 From: nicebounce AT trodman DOT com Message-Id: <200303062108.h26L8Kc5024836@tigris.pounder.sol.net> X-Authentication-Warning: tigris.pounder.sol.net: rodmant set sender to nicebounce AT trodman DOT com (Tom Rodman) using -f To: cygwin AT cygwin DOT com Fcc: usenet X-note: 1G0!G/usr/sbin/sendmail -v -t -f"nicebounce AT trodman DOT com (Tom Rodman)" # less traceable, bypasses MUA X-note: "From:" is usually added by MUA?, with "sendmail -f", no From header added X-note: if you define "From:" even your bogus def is always honored Reply-to: trodman AT nyx DOT net (Tom Rodman) Subject: {par script path}: {chld script path}: /bin/bash: bad interpreter: Permission denied Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Here's an error message example: /adm/bin/ccm_build_scripts/run_large_nb.sh: s:/adm/bin/ccm_build_scripts/run_nb.sh: /bin/bash: bad interpreter: Permission denied "run_nb.sh" aborts immediately, not executing a single line as far as I know. Misc info: $ pwd /adm/bin/ccm_build_scripts $ head -1 run_large_nb.sh run_nb.sh ==> run_large_nb.sh <== #!/bin/bash - ==> run_nb.sh <== #!/bin/bash - $ ls -l run_large_nb.sh run_nb.sh -rwxr-xr-x 1 adm_tsr SCM_ES_S 54021 Mar 3 11:15 run_large_nb.sh -rwxr-xr-x 1 adm_tsr SCM_ES_S 13322 Sep 3 2002 run_nb.sh $ uname -a;echo $CYGWIN CYGWIN_NT-5.0 c7mkes123 1.3.20(0.73/3/2) 2003-02-08 12:10 i686 unknown unknown Cygwin binmode ntsec tty The scripts involved have long been stable. The problem occurs sporatically. It happened early this week 3 times in one morning, then I rebooted the box and ran an intensive software build which exercised both scripts over a 22 hour period with no problems. Problem has been seen on both cygwin 17-1 and 20-1 (we skipped 18-1), I'm not convinced it's a cygwin problem. We're running Windows 2000 Server on all boxes involved; I believe our service packs are up to date. The scripts reside on a network drive "s:" controlled by an HP VA7400 SAN; perhaps the problem is SAN related. The SAN is seen by our remote w2k file server as a local SCSI block device. The SAN hardware is shared by many UNIX or Windows servers- each allocated separate LUNs. See cygwin mount table at end of e-mail. I can not force the error msg to occur at will even when I make the parent and/or child script nonexecutable. Does anyone know how to force the same error msg that we're getting? I've searched my local cygwin mailing list archives for this error, with no luck. Any insights would be appreciated. Since we run so long between occurances of this problem, I'm not too concerned. I wanted to at least document this somewhat for others that might see it. -- thanks/regards, Tom Rodman perl -e 'print unpack("u", "\.\=\$\!T\