Summary: | The init script of sys-apps/hal-0.5.5.1-r3 needs a start-stop-daemon which supports --use-syslog option | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sylvain BERTRAND <sylvain.bertrand> |
Component: | Current packages | Assignee: | Project Gentopia <gentopia> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | gnome, yvasilev |
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | /etc/init.d/hald patch |
Description
Sylvain BERTRAND
2005-12-30 17:42:43 UTC
incorrect.... re-emerge hal. Created attachment 75967 [details, diff]
/etc/init.d/hald patch
I think that the --use-syslog parameter is quite usefull, so it may be better if it have beed solved this way.
Yuri.
re-emerge! It's been fixed 3 days now people I know, and my patch is for the fixed init script. In it I wanted to keep the --use-syslog parameter to hald from the original init script. Yuri. Holy cow people.... I ADDDED IT ebegin "Starting Hardware Abstraction Layer daemon" if [ -f /proc/acpi/event ]; then chgrp haldaemon /proc/acpi/event chmod 440 /proc/acpi/event fi start-stop-daemon --start -q --exec /usr/sbin/hald -- --use-syslog eend $? } Just when I recopied it over, I forgot to include the -- so it didn't work. Which is why you opened this bug. It's fixed and done! Just stop. I think they feel this way as thier init scripts are possibly not being overwritten. Please delete the init script then emerge hal ... if you manually change the init script, the mtime info changes, and portage will *NOT* overwrite the file. Hi, Actually I was being plain stupid, so I apologize for it. My confusion was not to notice that the hald init script for hal 0.5 comes from sys-apps/hal/files/0.5-hald.rc and not from sys-apps/hal/files/hald. So after I synced portage tree I noticed no change/improvement. Yuri. |