broker_module=/usr/local/lib/mk-livestatus/livestatus.o /var/lib/nagios/rw/live
event_broker_options=-1

Y dentro del log de Nagios vamos a ver algo similar a esto
[1256144866] livestatus: Version 1.1.2 initializing. Socket path: '/var/lib
/nagios/rw/live'
[1256144866] livestatus: Created UNIX control socket at /var/lib/nagios/rw/
live
[1256144866] livestatus: Opened UNIX socket /var/lib/nagios/rw/live
[1256144866] livestatus: successfully finished initialization
[1256144866] Event broker module '/usr/local/lib/mk-livestatus/livestatus.o'
initializ
ed successfully.
[1256144866] Finished daemonizing... (New PID=5363)
[1256144866] livestatus: Starting 10 client threads
[1256144866] livestatus: Entering main loop, listening on UNIX socket

Opciones del módulo
Opción
debug

Valor por
default
0

max_cached_messages 500000

max_response_size

104857600

num_client_threads

10

thread_stack_size

65536

query_timeout

10000

Que significa
Set this to 1 in order to make
Livestatus log each query it
executes in nagios.log
Livestatus' access to Nagios logfiles
caches messages in-memory. Here
you can set the maximum number
of cached messages. Each message
takes about 250 bytes (in the
current implementation)
Livestatus constructs each response
in-memory before sending it to the
clients. In order to avoid a crash in
case of extensive queries, the
maximum response size is limited.
The default limit is 100 MB
Livestatus needs one thread for
each concurrent client connection. A
fixed number of threads is created
when Nagios starts
This parameter sets the size of the
stack of each client thread. In
versions before 1.1.4, the stack size
was set to 8 MB (pthread default).
The new default value is 64 KB. A
small stack reduces virtual memory
usage and also save CPU
ressources. A too small value will
probably crash your Nagios process,
though. You have been warned
This value is in ms. In order to avoid
being hung by broken clients,
Livestatus imposes a limit on the