[mythtv-users] Making sure HDHomeruns are available
stephen_agent at jsw.gen.nz
Tue Mar 21 01:37:46 UTC 2023
On Mon, 20 Mar 2023 17:56:26 +0000, you wrote:
>From: mythtv-users <mythtv-users-bounces at mythtv.org> on behalf of Ian Evans <dheianevans at gmail.com>
>Sent: 15 March 2023 16:41
>To: Discussion about MythTV <mythtv-users at mythtv.org>
>Subject: [mythtv-users] Making sure HDHomeruns are available
>Just wanted to check if the instructions found in https://www.mythtv.org/wiki/Silicondust_HDHomeRun_setup#Failure_after_system_reboot are the right ones to be using. First time testing an install on 20.04 as my previous setup didn't have systemd
>I created the mythbackendpre.sh mentioned in that wiki entry.
>When I went to create the /etc/systemd/system/mythtv-backend.service.d/override.conf file, it mentioned that the mythtv-backend.service.d directory didn't exist. Just being purposefully thick here, I assume I just create that directory and proceed?
>I am running 20.04 xubuntu and that folder existed on both my 'live' system with myth v32 and an old laptop with 20.04 and myth v34 development.
>Did you use Myth Control Panel to install Myth? I would expect that creating it yourself should work.
The systemd override folders /etc/systemd/system/<unit name>.d are not
automatically created unless you use the "systemctl edit <unit name>"
command to create the override file in the directory. Before the
"systemctl edit" command existed, you just created the <unit name>.d
directory manually, and that still works.
How it works is systemd looks for a /etc/systemd/system subdirectory
of the same name as the systemd unit, plus .d. If it finds that
directory, it will load all *.conf files in that directory, in
collating sequence order, and use them as overrides on the original
systemd unit file. If you want to disable an override file without
deleting it, just rename it to something other than *.conf. I usually
rename them to *.conf.not.
More information about the mythtv-users