| commit | 389594f6890d0403ff2e76e6dbc5cd75350a8697 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Mon Dec 12 22:35:57 2016 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Oct 01 21:28:29 2019 |
| tree | 69123874bc250bb615c60d6daf7eb45dfe3d7e90 | |
| parent | 5f4302621d8e011edbd83858b0c3183e29f842b5 [diff] |
daisydog: standardize exit paths Use err to display errno messages & exit. This standardizes the messaging & makes the code slightly smaller. BUG=None TEST=CQ passes Change-Id: I9184557b5841aa91691039c1babca3105c104761 Reviewed-on: https://chromium-review.googlesource.com/1829780 Tested-by: Mike Frysinger <vapier@chromium.org> Commit-Ready: Mike Frysinger <vapier@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Douglas Anderson <dianders@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.