You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2022. It is now read-only.
When auraed is started as pid1, it has no parent process in user space. It is then also called init process.
In case the init process stops, the kernel does not know what to do - so it panics.
I think we shouldn't let the kernel panic, and handle the two cases:
regular stop of auraed
unhandled rust panic / aka auraed crashes
A simple solution is to just shutdown the system via e.g.
syscall_reboot(libc::LINUX_REBOOT_CMD_POWER_OFF);
The text was updated successfully, but these errors were encountered:
When auraed is started as pid1, it has no parent process in user space. It is then also called init process.
In case the init process stops, the kernel does not know what to do - so it panics.
I think we shouldn't let the kernel panic, and handle the two cases:
A simple solution is to just shutdown the system via e.g.
The text was updated successfully, but these errors were encountered: