[mythtv-users] mythbackend won't idle until mythfrontend disconnects

[Max Barry]

James Stembridge wrote:
> If you specify a startup script in mythtv-setup then that will receive
> "auto" or "user" on the command line depending on whether the backend
> is about to start a recording. Note you only get "auto" if the "block
> shutdown before client connect" is enabled.

I'm afraid I'm stumped. I run into two different problems, depending on
whether "Block shutdown before client connected" is enabled or not:

(1) If it *is* enabled, then mythbackend helpfully writes into the log
either "Recording starts soon, AUTO-Startup assumed" or "Seem to be
woken up by USER". It then calls my startup script with the argument
"auto" or "user," just like it should. However, this is pointless,
because that "Block shutdown before client connects" setting means I
*have* start the frontend if I ever want mythbackend to realize it's
idle. So, regardless of whether my script gets "auto" or "user", it
needs to start mythfrontend. I guess I could make my script start
mythfrontend, then immediately terminate it if it's an "auto" start, but
this just seems ridiculous.

(2) If the setting is *not* enabled, then no helpful messages about
"AUTO" or "USER" startup appear in the log. Mythbackend does invoke my
startup script, but always with the argument "user," even if it woke
itself up.

I've inspected the MythTV 0.18 source (lines 937 - 962 of
programs/mythbackend/scheduler.cpp) and indeed this is the way it's
coded. The variable 'startupParam' is set to 'user' by default, and
unless 'blockShutdown' is enabled, it can never be 'auto'.

I can't work out what on Earth this accomplishes! It looks like a bug to me.

Now I'm wondering how your setup works, James. Is it 0.18?

Max.