summaryrefslogtreecommitdiffstats
path: root/reboot
Commit message (Collapse)AuthorAgeFilesLines
* reboot: only pause indefinitely for non-shutdown operationsMark Salyzyn2017-09-291-8/+12
| | | | | | | | | | | | | | | | | | | If -p flag specified, return immediately so that scripting code can progress. Shutdown is unique in that if it does happen, the device will never come back, but if it fails one can continue diagnosis (without the need for a script to send a SIGINT to break out of the indefinite pause on the reboot -p command). Yes, this will break adb shell reboot -p ; adb wait-for-device as noted in the comment, but no one should ever expect the device to come back if a shutdown is requested. We do not break adb reboot ; adb wait-for-device sequence though as we retain the pause forever. Test: manual Bug: 63736262 Bug: 38446744 Bug: 66912053 Change-Id: I028cd873a7193a78c6b3c342eca1e08b6b296fd2
* adb: reboot: last boot command defaultMark Salyzyn2017-09-121-0/+1
| | | | | | | | | For reboot [reboot_arg] requests via either reboot or adb reboot, if reboot_arg is empty then report "shell" or "adb" respectively. Test: boot_reason_test.sh shell_reboot adb_reboot Bug: 63736262 Change-Id: Ie613d9e62db6a705885e4e7520aede27af3aa1b9
* Convert more Android.mk files to Android.bpDan Willemsen2016-07-132-14/+8
| | | | | | | These modules have their dependencies satisfied, and aren't doing anything strange. Change-Id: I72039a15256cbd5e5eee0d79a15d66d74a6c087d
* reboot: Turn on -WerrorMark Salyzyn2014-05-211-4/+6
| | | | Change-Id: Ic3186e457b80ee6149ef89321b0d16422872aea7
* Use the getopt function in compliance with the standard.David Gumberg2014-03-021-1/+1
| | | | | | | | | | This is a simple change to the use of getopt in reboot.c, as per the standard, getopt does NOT return an EOF, it returns a -1, (this was done to remove getopt's dependence on stdio.h), and since the standard does not guarantee that EOF is -1, and the documentation tells us that getopt returns -1, in my judgement it would be best to test for -1, rather than EOF. Change-Id: I63a3bb7011eb60753eb910221bbe8ce0a71e6679 Signed-off-by: David Gumberg <davidzgumberg@gmail.com>
* Don't return immediately from reboot commands.Nick Kralevich2013-10-241-0/+5
| | | | | | | | | The reboot commands return too fast, interfering with testing. Add a pause(), which will allow the device time to complete the reboot. Change-Id: Ie9cc6eea67b7ff662ec71ea2329cbb94f8d55404 Bug: 11369303
* Make init handle rebootsNick Kralevich2013-04-231-19/+18
| | | | | | | | | | | | | | | | | | | | | Move the responsibility for rebooting the system from the reboot command to init. Init is in a better position to take actions to bring the system down cleanly, including making sure filesystems are mounted read-only. The only UIDs which can perform an init triggered reboot are root, system, and shell. Modify the reboot command so that it calls into init to perform the reboot. The reboot command no longer requires CAP_SYS_BOOT. Remove the -n reboot option and code which supports it. Anyone needing to do an unclean shutdown can just do a 'echo c > /proc/sysrq-trigger'. Modify adb so that it calls into init to perform a shutdown. Bug: 8646621 Change-Id: I84c0513acb549720cb0e8c9fcbda0050f5c396f5
* toolbox: Make reboot a separate command from toolboxBenoit Goby2013-03-262-0/+86
Set the CAP_SYS_BOOT filesystem capability on the new reboot command and keep CAP_SYS_BOOT in adb bounding set so that the shell user can run it. Change-Id: I1dd6143445ee2a952254f0452ab6e544318431dd