From freebsd-java  Thu Mar 20 22:53:47 2003
From: Brent Verner <brent () rcfile ! org>
Date: Thu, 20 Mar 2003 22:53:47 +0000
To: freebsd-java
Subject: Re: Specifying jdk for tomcat 4.1.18
X-MARC-Message: https://marc.info/?l=freebsd-java&m=104820083613232

[2003-03-20 19:33] Sheldon Hearn said:
| On (2003/03/20 08:13), Milo Hyson wrote:
| 
| [...HTML only...]
| 
| > I agree. At the very least, I would expect a FreeBSD port to provide
| > the option to behave like the official stock release.
| 
| Hang on, that's not what this is about.  Even with the XML config file
| approach, *ctl could still default to the VM for which it was built in
| the absence of that XML file.
| 
| What I'm saying is that an XML file doesn't seem justified, given that a
| simple, traditional solution alreayd exists for this kind of thing (an
| envar).

The problem is a little bigger than _just_ the JAVA_HOME env issue,
which is why I went the external configuration route....
(I am totally open to alternate config file formats)

In the current daemonctl.c program, the service in question
is started with the following C call.

execl("%%JAVA_HOME%%/%%JAVA_CMD%%", "%%JAVA_HOME%%/%%JAVA_CMD%%", 
      "-jar", %%JAVA_ARGS%% "%%JAR_FILE%%", %%JAR_ARGS%% NULL);

This works for tomcat, but I wasn't able to coerce jboss to start
using those same exec args; specifically, the jboss startup needs
a -classpath argument pair.  The problem I want to solve is how
to use the official startup script(s) in a sane manner through
the setuid/setgid daemonctl wrapper.

  b

-- 
"Develop your talent, man, and leave the world something. Records are 
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing."  -- Duane Allman

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message