Quote from: leenoox on February 09, 2018, 07:17:13 PM

Quote from: bytiges on February 09, 2018, 03:17:28 PM

@papampi:

I found a solution for starting watchdog from rc.local. Just call it like this:

Code:

(sleep 90 && systemctl restart watchdog.service)&

this will sleep a little before restarting watchdog, but it will do so in the background and allow for rc.local to terminate beforehand.

Now, on a intel mobo I'm loading the iTCO_wdt module and the dmesg output looks good:

Code:

[ 120.924534] iTCO_vendor_support: vendor-support=0
[ 120.927694] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 120.927729] iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x1860)
[ 120.927827] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)

bytiges.

I was looking to implement the iTCO_wtd a while back. Too preoccupied with other things...
Check this for testing iTCO:
http://www.madore.org/~david/linux/iTCO-wdt-test.html

@Leenoox
I seen that and it works manually but not auto starts.

@bytiges
Your 90 second sleep not works for me as I think my problem is with restart command, whatever I do it fails with restart.
I added 3 modprob modules to rc.local and now at startup watchdog showup in dev

Code:

modprobe i2c-i801
modprobe i2c-smbus
modprobe iTCO_wdt

Set watchdog.conf to ping my router
Now if I start watchdog manually and remove the network cable, watchdog reboots the rig after given time. (1 step ahead)

Tried to add a sleep to restart command between stop and start in /etc/init.d/watchdog and it still not starts and fails.
Only solution is to stop and start it again for me now.