When Not to Modify Defaults
Restoring Default Values with RESET ENVIRONMENT
Monitoring Dynamic Statistics
For example, if your server has a slow hard disk or insufficient RAM, you can
compensate temporarily by modifying defaults. The long-term solution is to
replace the disk or to add RAM. See
page
34.
If you were to modify some defaults, you could sacrifice the system's balance
and performance.
After thorough testing, we recommend, for example, that you do not modify
the default settings of the Load Balancing Threshold or the Transaction
Tracking parameters.
If you want to restore the default values of the settable server parameters, you
can use the RESET ENVIRONMENT command.
When you run RESET ENVIRONMENT, you are prompted at each changed
server parameter value.
At the System Console prompt, enter
RESET ENVIRONMENT
When the first parameter with modified values appears, you can choose to
reset all values to their defaults or just reset the value of the parameter that is
displayed. Or you can also skip to the next modified parameter.
For more information, see
MONITOR reports many useful statistics and updates most of them every
second with the return values from direct calls to the operating system.
However, not all statistics are of equal value to the network administrator. The
key dynamic statistics are displayed in MONITOR's General Information
screen, which appears as soon as MONITOR is accessed. For a description of
these statistics, see
"What to Monitor and Why" on page
NetWare Remote Manager and ConsoleOne
to monitor server performance.
"Matching Performance Capabilities" on
RESET ENVIRONMENT
are other utilities that allow you
TM
Optimizing the NetWare Server
in
Utilities
Reference.
83.
43
Need help?
Do you have a question about the NETWARE 6-DOCUMENTATION and is the answer not in the manual?
Questions and answers