Ticket #172 (closed defect: fixed)
Opened 16 months ago
Last modified 16 months ago
OpenRC fails to start HAL
Reported by: | egore@gmx.de | Owned by: | roy |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | rc | Version: | 0.4 |
Keywords: | Cc: |
Description
I had some trouble with HAL lately and so I removed it from my system to reinstall it. Before removing it was at runlevel default. After I installed HAL again it was not starting ater the reboot. It was just not showing up in the boot log. So I thought it was because it was removed from the runlevel during reinstallation. But it is present. I checked the following:
# rc-update | grep hald
hald | default
and
# ls -l /etc/runlevels/default/hald
lrwxrwxrwx 1 root root 16 May 3 18:21 /etc/runlevels/default/hald -> /etc/init.d/hald
But it is not started when entering runlevel default. So I thought: add it to "need" in xdm so it comes up. But doing so does not HAL to be started before xdm.
I have no idea why it is not started. It is even reported to be stopped:
# /etc/init.d/hald status
- status: stopped
And no sign of it could be found in /lib/rc/init.d
Can someone enlighten me what might stop HAL from starting?
(This all happens on a gentoo using openrc 0.4.3-r2)
Change History
comment:1 Changed 16 months ago by roy
comment:2 Changed 16 months ago by egore@gmx.de
This is the output after a fresh restart of my system:
egore912 ~ # /sbin/rc-service hald status * status: stopped egore912 ~ # /sbin/rc-update | grep hald hald | default egore912 ~ # /sbin/rc-service hald restart * Starting Hardware Abstraction Layer daemon... [ ok ]
As you can see it's listed in the default runlevel but for some reason it is not started. And for me it worked like a charm until I removed hal and reinstalled it. While I'm thinking about what I did:
- "/etc/init.d/hald start"
- "emerge -C hald"
- "reboot" (accidentially)
- "emerge hal"
Somewhere during this I think I put openrc into a state where it thinks the service is running when entering a runlevel while it actually isn't. Is there some difference in what "/sbin/rc-service hald status" returns and what is used to determine which services to start during a runlevel change.
comment:3 Changed 16 months ago by roy
If you run
rc-update -u
Does that help?
comment:4 Changed 16 months ago by egore@gmx.de
- Status changed from new to closed
- Resolution set to fixed
... and now it works! :-) Wonder what went wrong. But updating the service dependencies fixed it. Good point. Many thanks!
Works fine here.
What is the output of