IBM Enterprise Console manual Running Multiple UNIX Log File Adapters, Stopping the Adapter

Stopping the Adapter

Use the init.tecad_logfile stop command to manually stop the adapter. Always use this command to ensure that the syslogd daemon is correctly configured to stop sending messages to the adapter. If the adapter is stopped with any other method, the syslogd daemon might exit because the adapter is no longer listening on the named pipe the syslogd daemon is writing to.

Note: The endpoint adapter can be automatically stopped by distributing an ACP that has the adapter start command removed from the after-file-distribution actions. See the IBM Tivoli Enterprise Console User’s Guide for additional information.

Running Multiple UNIX Log File Adapters

You can run multiple instances of the UNIX log file adapter on a single system. It is recommended that additional adapters be run as non-TME adapters. To monitor different log files, each instance of the adapter must have its own configuration, format, class definition statement (CDS), and error files.

If you want to stop an adapter when multiple log files are running, you must specify the name of the adapter to stop. If you do not specify the adapter to stop, the default adapter without a name is stopped.

The syntax for the init.tecad_logfile command is the following:

init.tecad_logfile [–s] {start stop} [AdapterID] &

If the –sflag (skip syslog) is specified, the adapter does not monitor the syslogd daemon.

If the –sflag is not specified, use & so that the command runs in the background while returning a command prompt to your session. Otherwise, because an adapter started without the –soption forks a child process to run the adapter, the process does not return to the command line until the child process ends.

Note: If you start the adapter with the –sflag, you can also use the –sflag when you stop the adapter to avoid reconfiguring the syslogd daemon. You can also stop the adapter without the –sflag and it still works. However, do not stop an adapter with the –sflag if you did not start it with the –sflag.

If the –sflag is not specified, the UNIX log file adapter startup script uses a UNIX pipe to monitor the syslogd daemon and the syslogd daemon is configured to write to the pipe, and the UNIX log file adapter reads from that pipe. When the adapter ends, the startup script will reconfigure the syslogd daemon to stop writing to the pipe before stopping the UNIX log file adapter.

Do not configure more than one UNIX log file adapter to read from the syslogd daemon on a particular system.

The following command starts a UNIX log file adapter called syslog that monitors all syslog messages:

init.tecad_logfile start syslog &

102IBM Tivoli Enterprise Console: Adapters Guide