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.
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.