| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Commit fb9869ff introduced the concept of passing in a default interval
timeout to the watchdog application on startup. This utilized the
existing --min_interval option. This worked ok but it limited the
ability of external users to reduce the interval.
Give the above limitation, a new feature was added to phosphor-watchdog
which allows the user to explicitly set the default interval on startup
in the following commit:
https://github.com/openbmc/phosphor-watchdog/commit/afc369ad548137a5fdb0bc69b6606e2aafa7182b
Utilize this new parameter to set the default interval on startup.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Ia21dc7bb9dec50f3ec044c6d1733a54bcea15298
|
|
This commit will allow other meta layers to easily override the default
timeout on watchdog start. Without passing the --min_interval option
there is no way currently for other layers to change this on startup.
Set the default of 30000 milliseconds to match the current default
defined within the phosphor-dbus-interface.
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I6a25d5dd3da5704113c3f77d6f9737e0705b3d01
|
|
Per OpenBMC direction, hard code the path to the application
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I7dbbc9d8c353bc760d32e9cd106551a8bfab3838
|
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
