Does that mean the T2 will run as an mqtt client? If so, it could publish its current state regularly, rather than the RPi having to ping it. If it stops publishing, the RPi script intervenes with a power cycle. Or am I misunderstanding?
What am I not getting through here? How will the settop process crashing stop mtqq (whatever that is) running, when they are separate threads that run independently of each other? What's needed is to monitor something that is regularly written to while settop is running, eg 0.ts (except that doesn't get written to when it's a radio or data service).
You could use the IR package from the script you run to check if it is responsive but you might need to change channel to be able to detect the response which could be annoying if you are watching the box at the time
The difficulty is working out what that could be, under all circumstances.
Yes. Server/broker and/or client.
Why not go belt and braces? Yes, pinging / port 80 might catch some failures so you can take immediate corrective action, but for the ones which slip through do a nightly reboot anyway.
So are mine! Not so much because the TVs don't have Freeview tuners, but so they are instantly available to schedule recordings or whatever, and so the recordings on them are always available for streaming. If I implement a nightly shutdown, it will be briefly at about 4am: scheduled standby; power interruption; scheduled wake-up.
/mod filesystem is in trouble./mod filesystem: mount | grep -E "on /$(ls -l /mod | sed -ne 's@^l.* -> @@;s@/mod$@@;p') type ext[234] \(rw,"?PID="$(ls -l /proc/*/exe 2>&- | grep "/usr/bin/humaxtv" | cut -d'/' -f 3)"?lsof -p $PID (or similar) directly or just call status to check the health of the humaxtv process.status will also show if the HD/R is recording or about to record in case you want to force a reboot.#/bin/sh +m
# +m: disable job (aka background process) messages
timeout_child () { # (timeout); uses $! = last BG process
local child=$!
local timeout=$1
local timestep=1
[ -n "$child" ] || return
trap -- '' TERM KILL
( # use /proc to avoid variations in ps command
while [ -d "/proc/$child" ]; do
if [ $timeout -le 0 ]; then
kill -KILL $child
break
fi
sleep $timestep
timeout=$((timeout - timestep))
done
) &
wait $child
}
hdstatus="$(status & timeout_child 10)" || echo "status command failed or hung"Or in my case, the retort would be "Well, if we're talking about saving electricity, how about turning off your PC, your 2 laptops, 3 Raspberry Pi's, 2 printers, a scanner, a dozen chargers for various things, 3 assorted TVs in various rooms that we never watch but have been on standby for at least 8 years, your power supplies for time-lapse cameras, your various powered USB and ethernet hubs, and the night-time light on the landing?" "Er... I never installed the night-time light?" "Exactly!" Guilty as charged.The 'convincing answer' could be "To save some electricity my dear". But I suppose the latter half of the sentence could possibly get you a slap.
Yes, but there must also be a power on time.
Yes, as long as your polling cycle is long enough that you are not hitting it with a series of power interruptions. Just one, during the sleep time (which could be as short as a minute).
Yeah, that's the sort of thing I meant. I supposed a sharp blow to the left ear is so last century.
Thanks to everyone!