After updating the tool wrapper script I noticed, that it sources setenv
and that this might not be adequate.
Actually I don't know the common or possible use cases of the script and
searching didn't reveal much. Users typically set JVM size in setenv and
at least for the digest feature it would be counter productive. Assume
the system allocating another 1 Gig just for doing an MD5 hash ...
Any opinion whether we should drop sourcing setenv in the tool wrapper
script?
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
