| 1 | #
|
|---|
| 2 | # For a description of the syntax of this configuration file,
|
|---|
| 3 | # see scripts/kbuild/config-language.txt.
|
|---|
| 4 | #
|
|---|
| 5 |
|
|---|
| 6 | menu "System Logging Utilities"
|
|---|
| 7 |
|
|---|
| 8 | INSERT
|
|---|
| 9 |
|
|---|
| 10 | config SYSLOGD
|
|---|
| 11 | bool "syslogd"
|
|---|
| 12 | default y
|
|---|
| 13 | help
|
|---|
| 14 | The syslogd utility is used to record logs of all the
|
|---|
| 15 | significant events that occur on a system. Every
|
|---|
| 16 | message that is logged records the date and time of the
|
|---|
| 17 | event, and will generally also record the name of the
|
|---|
| 18 | application that generated the message. When used in
|
|---|
| 19 | conjunction with klogd, messages from the Linux kernel
|
|---|
| 20 | can also be recorded. This is terribly useful,
|
|---|
| 21 | especially for finding what happened when something goes
|
|---|
| 22 | wrong. And something almost always will go wrong if
|
|---|
| 23 | you wait long enough....
|
|---|
| 24 |
|
|---|
| 25 | config FEATURE_ROTATE_LOGFILE
|
|---|
| 26 | bool "Rotate message files"
|
|---|
| 27 | default y
|
|---|
| 28 | depends on SYSLOGD
|
|---|
| 29 | help
|
|---|
| 30 | This enables syslogd to rotate the message files
|
|---|
| 31 | on his own. No need to use an external rotatescript.
|
|---|
| 32 |
|
|---|
| 33 | config FEATURE_REMOTE_LOG
|
|---|
| 34 | bool "Remote Log support"
|
|---|
| 35 | default y
|
|---|
| 36 | depends on SYSLOGD
|
|---|
| 37 | help
|
|---|
| 38 | When you enable this feature, the syslogd utility can
|
|---|
| 39 | be used to send system log messages to another system
|
|---|
| 40 | connected via a network. This allows the remote
|
|---|
| 41 | machine to log all the system messages, which can be
|
|---|
| 42 | terribly useful for reducing the number of serial
|
|---|
| 43 | cables you use. It can also be a very good security
|
|---|
| 44 | measure to prevent system logs from being tampered with
|
|---|
| 45 | by an intruder.
|
|---|
| 46 |
|
|---|
| 47 | config FEATURE_SYSLOGD_DUP
|
|---|
| 48 | bool "Support -D (drop dups) option"
|
|---|
| 49 | default y
|
|---|
| 50 | depends on SYSLOGD
|
|---|
| 51 | help
|
|---|
| 52 | Option -D instructs syslogd to drop consecutive messages
|
|---|
| 53 | which are totally the same.
|
|---|
| 54 |
|
|---|
| 55 | config FEATURE_SYSLOGD_READ_BUFFER_SIZE
|
|---|
| 56 | int "Read buffer size in bytes"
|
|---|
| 57 | default 256
|
|---|
| 58 | range 256 20000
|
|---|
| 59 | depends on SYSLOGD
|
|---|
| 60 | help
|
|---|
| 61 | This option sets the size of the syslog read buffer.
|
|---|
| 62 | Actual memory usage increases around five times the
|
|---|
| 63 | change done here.
|
|---|
| 64 |
|
|---|
| 65 | config FEATURE_IPC_SYSLOG
|
|---|
| 66 | bool "Circular Buffer support"
|
|---|
| 67 | default y
|
|---|
| 68 | depends on SYSLOGD
|
|---|
| 69 | help
|
|---|
| 70 | When you enable this feature, the syslogd utility will
|
|---|
| 71 | use a circular buffer to record system log messages.
|
|---|
| 72 | When the buffer is filled it will continue to overwrite
|
|---|
| 73 | the oldest messages. This can be very useful for
|
|---|
| 74 | systems with little or no permanent storage, since
|
|---|
| 75 | otherwise system logs can eventually fill up your
|
|---|
| 76 | entire filesystem, which may cause your system to
|
|---|
| 77 | break badly.
|
|---|
| 78 |
|
|---|
| 79 | config FEATURE_IPC_SYSLOG_BUFFER_SIZE
|
|---|
| 80 | int "Circular buffer size in Kbytes (minimum 4KB)"
|
|---|
| 81 | default 16
|
|---|
| 82 | range 4 2147483647
|
|---|
| 83 | depends on FEATURE_IPC_SYSLOG
|
|---|
| 84 | help
|
|---|
| 85 | This option sets the size of the circular buffer
|
|---|
| 86 | used to record system log messages.
|
|---|
| 87 |
|
|---|
| 88 | config LOGREAD
|
|---|
| 89 | bool "logread"
|
|---|
| 90 | default y
|
|---|
| 91 | depends on FEATURE_IPC_SYSLOG
|
|---|
| 92 | help
|
|---|
| 93 | If you enabled Circular Buffer support, you almost
|
|---|
| 94 | certainly want to enable this feature as well. This
|
|---|
| 95 | utility will allow you to read the messages that are
|
|---|
| 96 | stored in the syslogd circular buffer.
|
|---|
| 97 |
|
|---|
| 98 | config FEATURE_LOGREAD_REDUCED_LOCKING
|
|---|
| 99 | bool "Double buffering"
|
|---|
| 100 | default y
|
|---|
| 101 | depends on LOGREAD
|
|---|
| 102 | help
|
|---|
| 103 | 'logread' ouput to slow serial terminals can have
|
|---|
| 104 | side effects on syslog because of the semaphore.
|
|---|
| 105 | This option make logread to double buffer copy
|
|---|
| 106 | from circular buffer, minimizing semaphore
|
|---|
| 107 | contention at some minor memory expense.
|
|---|
| 108 |
|
|---|
| 109 | config KLOGD
|
|---|
| 110 | bool "klogd"
|
|---|
| 111 | default y
|
|---|
| 112 | help
|
|---|
| 113 | klogd is a utility which intercepts and logs all
|
|---|
| 114 | messages from the Linux kernel and sends the messages
|
|---|
| 115 | out to the 'syslogd' utility so they can be logged. If
|
|---|
| 116 | you wish to record the messages produced by the kernel,
|
|---|
| 117 | you should enable this option.
|
|---|
| 118 |
|
|---|
| 119 | config FEATURE_KLOGD_KLOGCTL
|
|---|
| 120 | bool "Use the klogctl() interface"
|
|---|
| 121 | default y
|
|---|
| 122 | depends on KLOGD && PLATFORM_LINUX
|
|---|
| 123 | help
|
|---|
| 124 | The klogd applet supports two interfaces for reading
|
|---|
| 125 | kernel messages. Linux provides the klogctl() interface
|
|---|
| 126 | which allows reading messages from the kernel ring buffer
|
|---|
| 127 | independently from the file system.
|
|---|
| 128 |
|
|---|
| 129 | If you answer 'N' here, klogd will use the more portable
|
|---|
| 130 | approach of reading them from /proc or a device node.
|
|---|
| 131 | However, this method requires the file to be available.
|
|---|
| 132 |
|
|---|
| 133 | If in doubt, say 'Y'.
|
|---|
| 134 |
|
|---|
| 135 | config LOGGER
|
|---|
| 136 | bool "logger"
|
|---|
| 137 | default y
|
|---|
| 138 | select FEATURE_SYSLOG
|
|---|
| 139 | help
|
|---|
| 140 | The logger utility allows you to send arbitrary text
|
|---|
| 141 | messages to the system log (i.e. the 'syslogd' utility) so
|
|---|
| 142 | they can be logged. This is generally used to help locate
|
|---|
| 143 | problems that occur within programs and scripts.
|
|---|
| 144 |
|
|---|
| 145 | endmenu
|
|---|
