This property will cause the Wrapper to dump all of the environment variables
visible to the Wrapper, along with where the values originated.
It can be very useful to help debug environment related problems.
Defaults to the value of the wrapper.debug property
so it will be included in debug output by default.
It is fairly common that users have problems with their environment not being what was expected.
This property can be very powerful in helping to track down the source of such problems.
When running as a service on Windows 2000, the Wrapper will load all declared
system-wide environment variables stored in the registry when the Wrapper is first started.
If the USERNAME environment variable is defined,
the Wrapper will then load the environment for that user from the registry as well.
This is done to make it possible to make changes to the configured environment
and then make use of them without requiring a system reboot.
Prior to Wrapper version 3.5.5,
this reloading of the registries was done on all Windows versions,
but it is no longer necessary starting with Windows XP and 2003.
On UNIX, it is common for the Wrapper to have close to an empty environment
when launched on system startup.
The debug output starts with a source column which shows where the environment was set.
The values, left-to-right, show the order of the sources from which they can be set.
The final value will be used.
P - Defined in the parent process, ie the variable was set when the Wrapper was launched.
S - Defined in the system-wide Registry. (Windows 2000 only)
A - Defined in the account specific Registry. (Windows 2000 only)
W - Defined by the Wrapper on startup.
C - Defined within the Wrapper configuration file.
The following is an example of the environment output when run on Windows as a specified users.
Note that some of the variables are configured by system, others by the Wrapper, or Wrapper configuration,
and yet others are loaded from the registry both for the SYSTEM user and configured account.