lircd and systemctl on Debian Buster

I took a 4 year sabbatical on a sailboat. I'm back and I've upgraded to Debian Buster and am trying to get mythtv running again. I have everything working properly except for lirc. I can get it to work if I do the following steps manually after a reboot. (By "get it to work" I mean that /usr/bin/irsend is actually sending the command data instead of waiting for the two services to be in an operational state.)

Code:/usr/bin/systemctl stop lircd.socket lircd.service
/usr/bin/systemctl start lircd.socket lircd.serviceI have a "modinit" section in /etc/lirc/lirc_options.conf as follows to do a fixup on /dev/ttyS0 and create /dev/lirc0:
Code:[modinit]
code = /usr/bin/setserial /dev/ttyS0 uart none
code1 = /usr/sbin/modprobe lirc_dev
code2 = /usr/sbin/modprobe serial_irI've tried putting the two systemctl commands in /etc/lirc/lirc_options.conf as follows:

Code:[modinit]
code = /usr/bin/setserial /dev/ttyS0 uart none
code1 = /usr/sbin/modprobe lirc_dev
code2 = /usr/sbin/modprobe serial_ir
code3 = /usr/bin/systemctl stop lircd.socket lircd.service
code4 = /usr/bin/systemctl start lircd.socket lircd.serviceThat doesn't work and I have to remove "code3" and "code4" in order to easily stop and start the lircd stuff. So it appears that I am trying to do this in the wrong place during startup. I can't find anything in the documentation that gives me any help. In fact, it took me several days to even determine that stopping and starting the lircd.socket and lircd.service would get lirc working. It's possible that I've got something else wrong and this is just a symptom, but I can't figure out where to go from here. Anyone have any suggestions?

Bob