Good point. If it's a command line program, then the shell automatically
expands the variable before the JVM gets passed the value. But JRun is started
by reading in a bunch of settings from properties files. You might be able to
get around this on UNIX by adding this environment variable to the bin/jrun
script instead of the properties file.
Suresh, have you tried looking in bin/jrun for the appropriate place to add this
variable as an argument to the JVM? Take a look in there. I'll look too when I
get a chance.
Scott
> -----Original Message-----
> From: Luke Taylor [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 13, 2000 5:36 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Passing environment variables
>
>
>
>
> Scott Stirling wrote:
> >
> > I don't the JVM knows how to expand OS environment variables. Have you seen
> > that it can? I would expect it to take that argument as a literal
> string like
> > it did.
> >
>
> Doesn't this depend on the shell which is used to run the JVM, rather
> than the jvm itself? Presumably this should do the varible substitution
> for you before running the command. I've certainly used this kind of
> thing before with bash and so on without any problems. I use Jrun on
> NT, though, where it uses a .exe so it's not easy to work out what
> command line is being used, otherwise it would be easier to mess about
> with jvm parameters.
>
> Luke.
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
