Its the "$@" in the java calls. For some reason, Tru64 handles an empty
string as an argument differently and complains about it as an invalid
argument.
You can either pass an argument to the script ( -config works, as noted
below), or remove the "$@" in all the java calls, which means that can
never pass in an argument. Or modify the source to ignore it.
Dean
> > > and catalina.out shows:
> > >
> > > usage: java org.apache.catalina.startup.Catalina [
> > > -config {pathname} ] [ -debug ] [ -nonaming ] {
> > > start | stop }
>
>My problem exactly. I don't know if it is just Tru64 UNIX or others have
>the same problem, but either *startup.sh is broken* or there is something
>messy with shells on Tru64.
>
>The message Lee reported on the bottom is from Catalina and it simply
>states that the startup parameters were wrong. What must be added is
>"-config ${CATALINA_HOME}/conf/server.xml". For some reason, it must be
>explicitely stated on startup. So, on 4.03 I had to edit "startup.sh" line
>into this:
>
>exec "$PRGDIR"/"$EXECUTABLE" start -config ${CATALINA_HOME}/conf/server.xml
>
>Is org.apache.catalina.startup.Catalina supposed to "look around" for it's
>config file if not specifically stated on command line?
>
>Nix.
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
