Configuring Monitor Agent Log Settings - Novell GROUPWISE 8 - ADMINISTRATION Administration Manual

NOTE: To limit access on Linux, use the
when you start the Monitor Agent. For more information, see
Startup Switches," on page 1063
At the Windows
1 Click Configuration > HTTP.
2 In the Authentication box, select Require authentication to browse GW Monitor.
3 Fill in the fields:
User Name: Provide a username for the Monitor Agent to prompt for when a user attempts to
access the Monitor Web console.
Password: Provide a password for the Monitor Agent to prompt for when a user attempts
access. Repeat the password in the Password Confirm field.
For optimum security for the Monitor Web console, use the
switches, along with a certificate file, when starting the Monitor Agent. For more information,
see Chapter 67, "Using Monitor Agent Startup Switches," on page
Intruder Lockout Count: Specify the number of failed attempts the Monitor Agent should
allow before it stops prompting the potentially unauthorized user for a valid username and
password.
Intruder Lockout Period: Specify the number of minutes that must elapse before the user can
again attempt to access the Monitor Web console.
If a valid user gets locked out of the Monitor Web console, you can use Clear Lockout to grant
access before the intruder lockout period has elapsed.
4 Click OK to put the authentication settings into effect.

63.9 Configuring Monitor Agent Log Settings

The Monitor Agent writes to two different types of log files.
Event log files record error messages, status messages, and other types of event-related
messages.
History log files record dumps of all MIB values gathered during each poll cycle.
1024 GroupWise 8 Administration Guide
The intruder lockout functionality is not available on Linux.
Monitor Agent server console:
--httpmonuser and --httpmonpassword
Chapter 67, "Using Monitor Agent
/httpssl
startup switches
and /httpcertfile startup
1063.