Interpreter Text File Busy

Hello, We've seen a new type of failure in our nightly & rolling builds: /bin/sh -c /path/to/build/folder/Script-D02E2E8606DF865600595B32.sh /bin/sh: /path/to/build/folder/Script-D02E2E8606DF865600595B32.sh: / bin/sh: bad interpreter: Text file busy ** BUILD FAILED ** It doesn't happen all the time, so I assume it's some sort of race. Can anyone suggest why this would happen, or what could be done to fix it? Google only seems to suggest that it might be related to NFS, but that's probably not the case here, as both sources and build output is on a local volume. >I've come across the 'bad interpreter' message a number of times in >the past, and invariably its been a newline issue. Have a look at >the script (or the script that generates it) and check that it has >unix line endings.

在执行一个shell脚本时，遇到了“-bash:./killSession.sh: /bin/bash: bad interpreter: Text file busy”错误提示，如下所示： [oracle@DB-Server bin. 한 셸 스크립트 때 만났다'-bash:./killSession.sh: /bin/bash: bad interpreter: Text file busy'오류 팁 다음.

The top line should start '#!/bin/bash'. >>However, this obviously wouldn't explain the problem if it only >happens intermittently. It sounds a bit unlikely, as this script is auto-generated by Xcode. I have received another suggestion to try to disable Spotlight indexing. It makes a lot of sense, regardless of if it is related to this problem or not, so I'll try to do that.

Thanx, j o a r •. >'Text file busy' means that the program file in question is open >for writing (that is, 'text' here means program code, as I'm sure >many people will already have guessed); you can see this by writing >Download Autocad Lt Convert Text To Attribute Software. a short test program like the following I wonder if xcodebuild tripped over itself somehow.

Perhaps it didn't manage to close the file properly before trying to execute it? These machines are often under significant load, as they run a lot of builds. As it's only happened a few times so far, it's by no means a critical problem, but our nightly & rolling builds are really important for our whole organization - everyone is using them: Engineering, Q&A, Support. Besides the obvious problem with broken code, there always seems to be something messing with our builds - we're out of disk space, or we hit the process / fork limits, or the CVS checkout failed. For something so seemingly simple as automated builds, there are an amazing number of things that can go wrong!

Thanx for your input! >On 17 dec 2005, at 13.57, Alastair Houghton wrote: >>>Does one of the daily/monthly scripts try to pre-bind executables >>on the system volume, by any chance? >>Possibly, but unlikely - as it happened for two consecutive builds.

>I will correlate these errors with the system logs on that machine >and see if it can give some clue. >>>'Text file busy' means that the program file in question is open >>for writing (that is, 'text' here means program code, as I'm sure >>many people will already have guessed); you can see this by >>writing a short test program like the following >>I wonder if xcodebuild tripped over itself somehow. Perhaps it >didn't manage to close the file properly before trying to execute >it? These machines are often under significant load, as they run a >lot of builds. If I read the error message correctly, it was /bin/sh that was still open. That's why I assumed it must be pre-binding. It's the only reason I can think of that /bin/sh would have been open for writing.

Kind regards, Alastair.