Configuring the Subagent472 Red Hat Directory Server Administrator’s Guide • May 2005If this parameter is not specified, the agent will write its logfile to the samelocation as your subagent configuration file. The logfile will be namedldap-agent.log.Make sure that the user as whom your subagent is running has write permissionto this directory.serverThe server setting specifes a Directory Server instance that you want to monitor.You must use one server setting for each Directory Server instance. The subagentrequires at least one server setting to be specified in its configuration file. Theserver setting should be set to the absolute path to the log directory of theDirectory Server instance you would like to monitor. For example:server /opt/redhat-ds/slapd-phonebook/logsMake sure that the user as whom you are running your subagent has readpermission to this directory.Starting the SubagentOnce your master agent is running and you have created your subagentconfiguration file, you are ready to start the subagent. To start your subagent, youmust run the ldap-agent program, specifying your subagent configuration file asan argument. You must supply the absolute path to the configuration file:./ldapagent /opt/redhat-ds/ldap-agent.confIf you want to enable extra debug logging, you can specify the -D option duringstartup:./ldapagent -D /opt/redhat-ds/ldap-agent.confTo stop your subagent, you must use the kill command against its process ID.Your subagent will print its process ID in its logfile, or you can run ps -ef |grep ldap-agent to find the process ID.Testing the SubagentTo test your subagent, you can use the Net-SNMP toolkit command-line utilities,such as snmpwalk and snmpget. In order for these tools to display variable namesfor the Directory Server, you must configure them to load the Directory Server'sMIB file. The Directory Server's MIB file is located in server_root/plugins/snmp
