17717 2008-10-29 00:40:26 +0300 should report if it can't reconnect 2014-11-05 20:41:07 +0300 1 1 3 Distributions Branch 4.1 klogd unspecified all Linux CLOSED WONTFIX P2 normal --- 17250 1 imz nobody qa-4.1 oldest_to_newest 80390 0 imz 2008-10-29 00:40:26 +0300 klogd-1.4.1-alt28 As https://bugzilla.altlinux.org/show_bug.cgi?id=17250 has shown, failed reconnects of klogd (after syslogd restart) stay completely unnoticed for the administrator. (I have been living with this problem for years.) I suggest that a failed reconnect should be reported. (Even if https://bugzilla.altlinux.org/show_bug.cgi?id=17716 is implemented, there may be other reasons for a failure, and this should be reported.) Perhaps the most effective way would be to exit. Then, the exit will be noticed from outside, and in such cases, the init-script (or monit) could try to restart the daemon and send a message to syslog or whereever. (Actually, in my case, a restart would even resurrect klogd.) 148568 1 mike 2014-11-05 20:41:07 +0300 В 4.1/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф.