I'm writing a JVMPI profiler, but that doesn't actually matter.  The
overloads of Runtime.exec, that have the 3rd environment argument, do not
pass the current environment to the child process.  Thus if you want to add
anything to the environment (e.g. _JAVA_OPTIONS=-Xrunmjp), you have to also
add anything else you need (e.g. LD_LIBRARY_PATH).  It kinda sux.  In
general I've found Java to be bad at creating a managing child processes,
but I spose that goes with the territory of being portable.

Mike
> -----Original Message-----
> From: Jon Schewe [mailto:jpschewe at mtu.net]
> Sent: Saturday, August 31, 2002 10:30 PM
> To: Mike Bresnahan
> Subject: Re: [TCLUG-DEVEL] LD_LIBRARY_PATH
>
>
> What kind of Java application are you writing?  One of the
> reasons to use Java
> is that you don't have to mess with this stuff.  Otherwise you're
> generally
> better off writing it in C.  You do realize that Java is able to
> lookup system
> libraries on its own too?
>