Or the first line contains some non printable characters after bin/sh. This could be verified by od or a hex editor.
I doubt the second cause, this wouldn't typically lead to a 'bad interpreter' (At least in my expierience). > -----Original Message----- > From: John Turner [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 19, 2003 2:15 PM > To: Tomcat Users List > Subject: Re: Error when I starting Jakarta-tomcat > > #!/bin/sh > > My guess is that on your system, either /bin/sh does not > exist, or the > permissions on $TOMCAT_HOME/bin/startup.sh do not allow the > script to be executed. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
