Hello,
On 01/05/12 10:02, Bastian Bittorf wrote:
would'nt it be senseful to adjust "START=01" to
/etc/init.d/watchdog
and place something like this?
pid="$( pidof watchdog )"
echo "1000">/proc/$pid/oom_score_adj
yeah, could do this.
I did this on my boxes, but it does not help.
Again a device is _pingable_, but all daemons are
not responding anymore:
dropbear, uhttpd, netperf, dnsmasq, (crond)
i have no idea why the above oom_score-thingy
did not work - thats all i can say. it's time for ar more
robust solution:
# call it once at startup
watchdogger -d /dev/watchdog --timeout 90
# call this in cron.minutely
watchdogger -d /dev/watchdog --kick
# do all checks with cron-called scripts
if cron fails, the watchdog will reboot the device.
if you are more conservative, use timeout 900
What about just using panic_on_oom?
bye, Bastian.
PS: someone has time to make a "watchdogger.c" ?
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
