Re: [Wrapper-user] scripts on mac os x

[Andy B. <aba...@ca...>]

I just realized that if I try to execute the binary wrapper executable 
rather than the shell script I get the same message you saw:

> bash-2.05b$ file *
> wrapper-linux:   ELF 32-bit LSB executable, Intel 80386, version 1 
> (SYSV)
> wrapper-macosx:  Mach-O executable ppc

> bash-2.05b$ ./wrapper-linux
> bash: ./wrapper-linux: cannot execute binary file

> bash-2.05b$ ./wrapper-macosx
> Usage: ./wrapper-macosx <file> [configuration properties] [...]

Is it possible you accidently copied the binary file instead of the 
shell script and you are now trying to execute the binary file rather 
than the shell script?

---
Andy Barnett <aba...@ca...>
Cantilever Technologies
---

On Apr 14, 2004, at 10:45 AM, Dan Weston wrote:

> I've used the service wrapper to deploy the same java app on windows, 
> linux, and solaris. I am now moving it over to Mac OS X. I'm having a 
> problem with the startup script that resides in the bin directory of 
> the service wrapper deployment hierarchy. From a terminal window in OS 
> X (Panther 10.3.3) , trying to start the script gets an error:
>
> -bash: ./taskserver: cannot execute binary file
>
> This is the exact same script that I use on all the other platforms. 
> The strange thing is that if I copy the contents of the script into a 
> fresh text file and save it, then I can run the copied script just 
> fine. So that makes me think that the contents of the script file are 
> fine, but there is something missing or wrong about the metadata for 
> the script file.
>
> Has anyone else run into this?
>
> thanks.
>
> Dan Weston