Well, they are JVM system variables so it isn't so much that
ResinWatchdogManager would pass them to the server, but that they're set in
the JVM when it's started and anything in that runtime instance will have
them available. My startup script uses this technique and it works great.
I suppose it is possible that a later version changed this behavior (we're
still on 3.0.21) but I'd be extremely surprised if that's the case.
On Mon, Nov 30, 2009 at 1:25 PM, Aaron Freeman <aaron.free...@layerz.com>wrote:
> > Aaron,
> > Maybe I am missing something, but if you can pass in
> > -Dconfiguration=wherever to your individual machines (in your
> > /etc/init.d/resin script or wherever, I assume?), can't you pass in
> > your server specific JVM args there too?
> > Rachel
> Probably. The configuration is passed in via an environment variable,
> but I could pass those in dynamically too if I have too. If we set
> those from our resin script will the ResinWatchdogManager pass the same
> values to the actual Resin server, when it launches it? I wasn't sure,
> so I was just going by the example resin.conf file that comes with Resin
> resin-interest mailing list
resin-interest mailing list