Bug 17717

Summary: should report if it can't reconnect
Product: Branch 4.1 Reporter: Ivan Zakharyaschev <imz>
Component: klogdAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED WONTFIX QA Contact: qa-4.1 <qa-4.1>
Severity: normal    
Priority: P2    
Version: unspecified   
Hardware: all   
OS: Linux   
Bug Depends on:    
Bug Blocks: 17250    

Description Ivan Zakharyaschev 2008-10-29 00:40:26 MSK

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 Michael Shigorin 2014-11-05 20:41:07 MSK
В 4.1/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф.