23179 2010-03-18 15:02:39 +0300 do not lookup hostnames (an option) 2019-06-19 02:07:02 +0300 1 1 4 Development Sisyphus syslogd unstable all Linux CLOSED WONTFIX P3 enhancement --- 21966 1 imz legion evg glebfm ldv legion mike qa-sisyphus oldest_to_newest 107909 0 imz 2010-03-18 15:02:39 +0300 syslogd-1.4.1-alt27 Actually, the non-working option mentioned in https://bugzilla.altlinux.org/show_bug.cgi?id=21966 would be quite useful: # -x Disables DNS lookups on messages recieved with -r. Because now the logging of remote messages coming from a host without a lookupable hostname is a terrible: it takes 5 secs (or sometimes more) waiting for the hostname, so the messages that come immediately one after another get logged with an interval of 5 sec (or sometimes more), and the logging of, say, 100 instantaneous messages takes a very very long time! 109173 1 mike 2010-05-12 19:31:46 +0400 It's a somewhat documented (and sometimes crucial indeed) option: $ cat /etc/sysconfig/syslogd # Options to syslogd # -m 0 Disables 'MARK' messages. # -r Enables logging from remote machines. # -x Disables DNS lookups on messages recieved with -r. # # See syslogd(8) for more details. SYSLOGD_OPTIONS='-u syslogd -j /var/resolv -r -x' # service syslogd reload Stopping system logger service: [ DONE ] Starting system logger service: /sbin/syslogd: invalid option -- x usage: syslogd [-drvh] [-l hostlist] [-m markinterval] [-n] [-p path] [-s domainlist] [-f conffile] [-i IP address] [-u username] [FAILED] Was it a 3rd party patch (with corresponding sysconfig file modification) but being async-dropped afterwards? 109183 2 mike 2010-05-12 22:31:59 +0400 ...or is sysconfig stuff rsyslogd-related?.. 182563 3 ldv 2019-06-19 02:07:02 +0300 Пакет был удалён в августе прошлого года: http://git.altlinux.org/tasks/archive/done/_207/211999/