-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hwclock[TIME plugins] failed to execute #110
Comments
Hmm, that should not be a problem as long as the kernel is built with |
Confirm. My suggestion is making it a task. EDIT: btw, i think this should be changed to a run/task too, since udevd may not run at the time.
|
The hwclock plugin could possibly as a task ... but for my embedded systems I'd really want it to run as soon as possible so kernel + userspace have the correct time. But I'll look into it. The udev-finish thing is currently not possible to move to a run/task because the event loop starts too late. I've been meaning to try to start the event loop much earlier to facilitate relocating parts of the boot process to run/tasklets in the bootstrap runlevel. It's on the TODO list ... sorry. |
I see, maybe make both methods available at the same time, that's also a good workaround. But yes, redesign to let event loop start really earlier is the best solution. We could even make a more generic system to replace plugin&service system if that's possible, so that tty/plugin in c/service/task or so, could all be controlled by one single system, simple and efficient. It's not a big deal, no matter :). |
I think you should check whatever /dev/rtc* exists before running If you don't find any just print a message an that is .. |
@abucodonosor Yup, and we should probably add |
But it works once my system get started. My guess is that it lacks a
/dev/xxx
before udevd started. Do you have any idea on how to adjust the order?The text was updated successfully, but these errors were encountered: