Bug 17717 - should report if it can't reconnect
: should report if it can't reconnect
Status: CLOSED WONTFIX
: Branch 4.1
(All bugs in Branch 4.1/klogd)
: unspecified
: all Linux
: P2 normal
Assigned To:
:
:
:
:
: 17250
  Show dependency tree
 
Reported: 2008-10-29 00:40 by
Modified: 2014-11-05 20:41 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-10-29 00:40:26
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.)
------- Comment #1 From 2014-11-05 20:41:07 -------
В 4.1/branch исправления не будут вноситься уже технически (заглушена очередь
на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на
текущие ветки или сизиф.