OpenELEC - ssh reboot versus XBMC restart

[donf99]

I've looked around the web for a definitive answer to this question, but have been unable to find one.
I am currently running OpenELEC 2.99.2 on an RPi.

Occasionally an add-on, like Navi-X, will hang so that it is not possible to get back to the home screen to perform a shutdown or reboot from the GUI.

In this case, it is usually possible to ssh to the Rpi and issue the reboot command to restart the card.

As another option, I remapped two MCE infrared remote control keys to perform the following:

<reverse>XBMC.Reboot</reverse>
<power>XBMC.RestartApp</power>

With this arrangement, I can force a reboot of the RPi with the remote's "reverse" transport key or just restart XBMC (without rebooting) with the remote's power key.

What is the difference between a hard reset by power cycling, a reboot via ssh or remote control, and an XBMC restart?

I would like to know if the OpenELEC ssh reboot command is any safer than pulling the power and resetting the board. Does the reboot command shutdown the card in a orderly fashion by killing off processes and unmounting the filesystem? Does an XBMC restart force a firmware uograde or apply remote.xml changes like a reboot would?

Thanks,

Don

[sdjf]

I do not know about OpenELEC specifically, but I do know that if you yank the power cord without properly shutting down the system, usually with something like the poweroff command first, you are highly likely to corrupt the file system. You can examine your logs to see what happens, if locations are the same as other distros, try /var/log/kernel.log and /var/log/everything.log