Bug 17716 - shouldn't start if not enough rights to reconnect
Summary: shouldn't start if not enough rights to reconnect
Status: CLOSED WONTFIX
Alias: None
Product: Branch 4.1
Classification: Distributions
Component: klogd (show other bugs)
Version: unspecified
Hardware: all Linux
: P2 normal
Assignee: Nobody's working on this, feel free to take it
QA Contact: qa-4.1@altlinux.org
URL:
Keywords:
Depends on:
Blocks: 17250
  Show dependency tree
 
Reported: 2008-10-29 00:31 MSK by Ivan Zakharyaschev
Modified: 2014-11-05 20:41 MSK (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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, перевесить на текущие ветки или сизиф.