| commit | 5f4302621d8e011edbd83858b0c3183e29f842b5 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Mon May 21 03:44:19 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue May 22 10:19:24 2018 |
| tree | 3a92d9e0ac770d7a2c09db6b7c1801082e1dfefe | |
| parent | 96d9e30fdfb7ab8b0cdc44228359dd0c08d59946 [diff] |
daisydog: use minimalistic-mountns minijail profile The only thing we need access to is /dev/watchdog. BUG=None TEST=starting daisydog still works, and killing it -9 causes system to reboot Change-Id: I5d10636226eb5c13550f77f3af1fca8906842365 Reviewed-on: https://chromium-review.googlesource.com/1067159 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
GPL Code is copied with explicit permission from Daniel Widyanto:
http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/
The project name is based on Samsung's “daisy” reference board design and I liked this quote from the daisy dog FAQ:
Daisy Dogs are not persnickety little ankle biters
When this daisydog doesn't run, the machine should reset. :)
An alternative code to start with would have been:
https://dev.openwrt.org/ticket/2270
The watchdog project is alot more complicated than what the Chromium OS project needs.