17716 2008-10-29 00:31:58 +0300 shouldn't start if not enough rights to reconnect 2014-11-05 20:41:06 +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 80388 0 imz 2008-10-29 00:31:58 +0300 klogd-1.4.1-alt28 As https://bugzilla.altlinux.org/show_bug.cgi?id=17250 has shown, on start, klogd first connects to the socket, and then drops priviledges. Even if it would have not enough rights to (re-)connect to the socket in the normal state (without the priveledges). This leads to errors in configuration not being easily discovered: externally, everything looks fine, but after a syslogd restart, klogd is running can't post the messages anymore. (I have been living with such an error for many years.) I suggest that the necessary permissions are checked on klogd as strictly as they will be checked on re-connect. So that any problem will be discovered on startup. 80391 1 imz 2008-10-29 00:40:55 +0300 A related suggestion: https://bugzilla.altlinux.org/show_bug.cgi?id=17716 . 148567 2 mike 2014-11-05 20:41:06 +0300 В 4.1/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф.