CAP_SINGLE*

Return to Home Page

The compile-time declarations described on this page restrict (as opposed to expand or extend) Syslogd2's run-time operational capabilities. By defining all three, with no other options, the resulting binary will be restricted to:

1. A single socket-processing thread
2. The default parent thread

.... which is as close as Syslogd2 can get to single-threaded operation. Defining these options may be desirable for laptops or stand-alone desktops where the syslog daemon resource footprint is to be minimized and syslog processing de-emphasized.
The socket-processing thread will support the default log socket at /dev/log and (if inet is enabled) a single UDP/IP socket on all interfaces (IP-address ' * '), using UDP port 514 .
Note that even though inputs are restricted, Syslogd2 will still support other CAP_*-abilities such as filters, spooling, name-cache, worker-threads, output-threads, etc.

CAP_SINGLEPORT

CAP_SINGLETHREAD

CAP_SINGLEPOOL

Return to top

CAP_SINGLEPORT

Return to top
The CAP_SINGLEPORT option prevents the use of any user-defined input socket other than the default IP and Linux sockets (' *.syslog ' as the default IP socket on UDP port 514 or '/dev/log' as the default system (Linux datagram) socket.
The CAP_SINGLEPORT declaration does not prevent the declaration or specification of non-socket (text-file or kernel) inputs. There are no run-time parameters associated with CAP_SINGLEPORT.
Return to top

CAP_SINGLETHREAD

Return to top
The CAP_SINGLETHREAD option limits the thread-count for all thread-pools (of any and all types) to a value of 1 (one).

There are no run-time parameters associated with CAP_SINGLETHREAD.
Return to top

CAP_SINGLEPOOL

Return to top
The CAP_SINGLEPOOL option limits the thread-pool count of each type of thread-pool to 1 (one). One socket-input thread-pool. One tailfile thread-pool. One worker thread-pool. One output thread-pool. This setting does not affect those thread-pool types that are already limited to one thread-pool (Housekeeping, Kernel-input, User-terminal-output). This restriction is accomplished by setting all thread-pool-id configurations to zero.
The thread-counts of individual thread-pools are unaffected by this setting. To restrict the number of threads-per-threadpool, see CAP_SINGLETHREAD.

There are no run-time parameters associated with CAP_SINGLEPOOL.
Return to top

Return to Home Page