Summary: | sys-apps/baselayout-vserver-1.12.3 (?) breaks startup of klogd | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcel Meckel <gentoo.org> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcel Meckel
2006-10-25 04:59:05 UTC
After digging a bit deeper i found a simple workaround but i'm not sure if this is an elegant way to handle this: Adding --oknodo to the start-stop-daemon call in the start_daemon() function in /etc/init.d/sysklogd is a way to do this. # start-stop-daemon --help Exit status: 0 = done 1 = nothing done (=> 0 if --oknodo) 3 = trouble 2 = with --retry, processes wouldn't die any thoughts about this workaround? vserver does not support klogd by default since the necessary system call is not available for guests.. if you really need klogd (there shouldn't be any reason, since you have no log message from the kernel inside) you can enable a stub interface to klogd with the SYSLOG ccapability... You don't understand - the sysklogd init-script is the same, in a vps or real server environment. with older versions of baselayout klogd was started and then exited but the init-script continued since start-stop-daemon thought it did his job well done. but now start-stop-daemon recognizes that klogd has exited and fails. i don't need klogd in a vps but the init-script from sysklogd tries to start it and someone has to make it right - baselayout guys or sysklogd maintainer. someone remind me why this is a bug maybe because it breaks all vps? why do you think it's not a bug? please read comment #3 carefully and try to understand why this is a serious bug which needs attention - either by baselayout-devs or sysklogd maintainer. dont cc me i fail to see this as a bug ... if klogd shouldnt be run in vps, then it shouldnt be in the runlevel Then maybe you could explain how i am supposed to start syslogd without klogd? it's not about me - i simply fixed the init-script with --oknodo on all vps. it's about the people installing or (even worse) upgrading and breaking things. i agree with you, klogd should not be run in a vps. do i have to file another "enhancement" report to get this issue addressed? yes, you should file another bug to control startup of klogd it is not a bug in ssd as ssd is doing exactly what it should be: reporting a failure when the daemon fails to start properly |