Hello,
I m working on IOT device dell gateway in that Ubuntu Core 16 OS is there and I want to use Hardware Timer for any unexpected crashes or etc…
So I have opened “/dev/watchdog” but it will busy always and get failed.
So i don’t know why its happening , is there any security in Ubuntu Core 16 to access some path.
and
2) I have tried some command to change RunTimeWatchdogSec but It could same nothing change.
In Dell gateway User manual there is one WDT and it is provide some Enable/Disable policy and some configuration files like /etc/systemd/system.conf.d etc… so IF i m enable this Timer so after words is that working same as our OS WDT ???
According to the output, the watchdog timer is configured and working.
If the manual says the watchdog timer is configured through /etc/systemd/system.conf.d/SOMEFILE.conf, you should follow it, otherwise the setting may become inconsistent.
And, YES, the watchdog timer is system-wide like what you want to do.
Actually I have one Main Application(Gateway App) and one watchdog Application(working as Daemon ) so watchdog App would be continuously eye on Main App(Gateway App) if something goes wrong i GatewayApp or crash happen then Watchdog App will restart it.
So Now the point is IF my Watchdog App will hang or some kill it then who has taken care SO I want to handle through OS timer.
BUT when I open “/dev/watchdog” open then it will GIVE error “Resource Busy”.
snap set core watchdog.runtime-timeout=1m
IF I set above parameter then How to know OS timer to WHEN restart the system untill OS was not hang.
Actually my Use case is mention above.
please Update me …
if you have that time set the OS will automatically restart via the builtin kernel mechnism … if you need to know the value in your application this would only be doable via something like:
snap get system watchdog.runtime-timeout
but i fear outside of that manual snap get... command you can only obtain the value via the snapd-control interface from an API call …