[package] resolveip: fix whitespace

[openwrt.git] / package / busybox / config / sysklogd / Config.in

diff --git a/package/busybox/config/sysklogd/Config.in b/package/busybox/config/sysklogd/Config.in
index 9eebd77..c7bac93 100644 (file)
--- a/package/busybox/config/sysklogd/Config.in
+++ b/package/busybox/config/sysklogd/Config.in
@@ -1,3 +1,4 @@
+# DO NOT EDIT. This file is generated from Config.src
 #
 # For a description of the syntax of this configuration file,
 # see scripts/kbuild/config-language.txt.
@@ -5,19 +6,21 @@
 
 menu "System Logging Utilities"
 
+
+
 config BUSYBOX_CONFIG_SYSLOGD
        bool "syslogd"
        default y
        help
          The syslogd utility is used to record logs of all the
-         significant events that occur on a system.  Every
+         significant events that occur on a system. Every
          message that is logged records the date and time of the
          event, and will generally also record the name of the
-         application that generated the message.  When used in
+         application that generated the message. When used in
          conjunction with klogd, messages from the Linux kernel
-         can also be recorded.  This is terribly useful,
+         can also be recorded. This is terribly useful,
          especially for finding what happened when something goes
-         wrong.  And something almost always will go wrong if
+         wrong. And something almost always will go wrong if
          you wait long enough....
 
 config BUSYBOX_CONFIG_FEATURE_ROTATE_LOGFILE
@@ -35,13 +38,31 @@ config BUSYBOX_CONFIG_FEATURE_REMOTE_LOG
        help
          When you enable this feature, the syslogd utility can
          be used to send system log messages to another system
-         connected via a network.  This allows the remote
+         connected via a network. This allows the remote
          machine to log all the system messages, which can be
          terribly useful for reducing the number of serial
-         cables you use.  It can also be a very good security
+         cables you use. It can also be a very good security
          measure to prevent system logs from being tampered with
          by an intruder.
 
+config BUSYBOX_CONFIG_FEATURE_SYSLOGD_DUP
+       bool "Support -D (drop dups) option"
+       default n
+       depends on BUSYBOX_CONFIG_SYSLOGD
+       help
+         Option -D instructs syslogd to drop consecutive messages
+         which are totally the same.
+
+config BUSYBOX_CONFIG_FEATURE_SYSLOGD_READ_BUFFER_SIZE
+       int "Read buffer size in bytes"
+       default 256
+       range 256 20000
+       depends on BUSYBOX_CONFIG_SYSLOGD
+       help
+         This option sets the size of the syslog read buffer.
+         Actual memory usage increases around five times the
+         change done here.
+
 config BUSYBOX_CONFIG_FEATURE_IPC_SYSLOG
        bool "Circular Buffer support"
        default y
@@ -50,14 +71,14 @@ config BUSYBOX_CONFIG_FEATURE_IPC_SYSLOG
          When you enable this feature, the syslogd utility will
          use a circular buffer to record system log messages.
          When the buffer is filled it will continue to overwrite
-         the oldest messages.  This can be very useful for
+         the oldest messages. This can be very useful for
          systems with little or no permanent storage, since
          otherwise system logs can eventually fill up your
          entire filesystem, which may cause your system to
          break badly.
 
 config BUSYBOX_CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE
-       int "    Circular buffer size in Kbytes (minimum 4KB)"
+       int "Circular buffer size in Kbytes (minimum 4KB)"
        default 16
        range 4 2147483647
        depends on BUSYBOX_CONFIG_FEATURE_IPC_SYSLOG
@@ -71,12 +92,12 @@ config BUSYBOX_CONFIG_LOGREAD
        depends on BUSYBOX_CONFIG_FEATURE_IPC_SYSLOG
        help
          If you enabled Circular Buffer support, you almost
-         certainly want to enable this feature as well.  This
+         certainly want to enable this feature as well. This
          utility will allow you to read the messages that are
          stored in the syslogd circular buffer.
 
 config BUSYBOX_CONFIG_FEATURE_LOGREAD_REDUCED_LOCKING
-       bool "logread double buffering"
+       bool "Double buffering"
        default n
        depends on BUSYBOX_CONFIG_LOGREAD
        help
@@ -92,10 +113,26 @@ config BUSYBOX_CONFIG_KLOGD
        help
          klogd is a utility which intercepts and logs all
          messages from the Linux kernel and sends the messages
-         out to the 'syslogd' utility so they can be logged.  If
+         out to the 'syslogd' utility so they can be logged. If
          you wish to record the messages produced by the kernel,
          you should enable this option.
 
+config BUSYBOX_CONFIG_FEATURE_KLOGD_KLOGCTL
+       bool "Use the klogctl() interface"
+       default y
+       depends on BUSYBOX_CONFIG_KLOGD && BUSYBOX_CONFIG_PLATFORM_LINUX
+       help
+         The klogd applet supports two interfaces for reading
+         kernel messages. Linux provides the klogctl() interface
+         which allows reading messages from the kernel ring buffer
+         independently from the file system.
+
+         If you answer 'N' here, klogd will use the more portable
+         approach of reading them from /proc or a device node.
+         However, this method requires the file to be available.
+
+         If in doubt, say 'Y'.
+
 config BUSYBOX_CONFIG_LOGGER
        bool "logger"
        default y
@@ -103,8 +140,7 @@ config BUSYBOX_CONFIG_LOGGER
        help
            The logger utility allows you to send arbitrary text
            messages to the system log (i.e. the 'syslogd' utility) so
-           they can be logged.  This is generally used to help locate
+           they can be logged. This is generally used to help locate
            problems that occur within programs and scripts.
 
 endmenu
-