| Summary: | sys-apps/openrc-0.2-r1 abandons clock which is still used | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Väth <martin> |
| Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED INVALID | ||
| Severity: | trivial | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
the hwclock init.d script has "provide" clock > the hwclock init.d script has "provide" clock
Then perhaps something else is strange: I ran into the problem because
I read a message like "...atd depends on nonexisting service clock...".
But perhaps this happened only at the first boot - I cannot reproduce it
anymore.
|
sys-apps/openrc-0.2-r1 apparently renamed /etc/{init.d,conf.d,/runlevel/boot}clock to *hwclock. However, clock is still used by some init-scripts e.g. atd, dcron, or metalog. Moreover, openrc itself has "after clock" in bootmisc and fsck dependencies.