Bug 17716

Summary: shouldn't start if not enough rights to 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:31:58 MSK 
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.
Comment 1 Ivan Zakharyaschev 2008-10-29 00:40:55 MSK 
A related suggestion: https://bugzilla.altlinux.org/show_bug.cgi?id=17716 .
Comment 2 Michael Shigorin 2014-11-05 20:41:06 MSK 
В 4.1/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф.