| 1 |
On Mon, Dec 1, 2014 at 12:46 PM, <meino.cramer@×××.de> wrote: |
| 2 |
> What is the difference here? |
| 3 |
> Isn't it, that all shutdown applications only send some instructions |
| 4 |
> to the kernel and the kernel is the main actor in bringing the system |
| 5 |
> down? |
| 6 |
> |
| 7 |
|
| 8 |
About the only thing the kernel might have a role in is turning off |
| 9 |
the power. Almost all of the shutdown logic is in userspace and it |
| 10 |
isn't surprising that copying scripts between distros is going to |
| 11 |
cause issues since the whole service management component varies |
| 12 |
GREATLY across distros. Maybe if you're using systemd you could copy |
| 13 |
between distros since that is more standardized, but even then there |
| 14 |
can be differences. |
| 15 |
|
| 16 |
In a traditional sysvinit system usually shutting down is accomplished |
| 17 |
by changing runlevels, which immediately starts/stops anything in |
| 18 |
inittab (generally only gettys) and calls a script which does all the |
| 19 |
actual work. |
| 20 |
|
| 21 |
If the issue is that userspace shuts down fine but the system reboots |
| 22 |
instead of powering off that could be a couple of things which |
| 23 |
shouldn't be too hard to track down. An obvious question is whether |
| 24 |
the hardware even supports being powered off in the first place - this |
| 25 |
isn't an ATX motherboard. Powering off a system can sometimes be |
| 26 |
remarkably tricky depending on how standardized the platform is. I |
| 27 |
was reading an article on it a few years ago and I think linux |
| 28 |
actually implements several different mechanisms that get tried in |
| 29 |
series, with the final fallback being a halt without powering off. |
| 30 |
|
| 31 |
-- |
| 32 |
Rich |
Archives