[mythtv-users] lircd setup with hdhomerun kludge

[Allen Edwards]

Sometimes going for a long walk is a good thing.  I did and then issued
this command:

sudo /lib/systemd/systemd-sysv-install enable lirc

Now my remote is back and I am happy to leave the kludge in.

Allen

On Tue, Aug 21, 2018 at 10:10 AM, Allen Edwards <allen.p.edwards at gmail.com>
wrote:

> Hope this doesn't double post.  I changed the subject and my mail server
> complained so here it is in the same thread.
>
> My remote is now dead and I don't know how to get back to where I was.
> Please help me.
> --------------------------------------------------------------
>
> OK, gave that command a try and it doesn't look good.
>
> allen at MythNew:/etc$ sudo systemctl disable lirc
> [sudo] password for allen:
> lirc.service is not a native service, redirecting to systemd-sysv-install
> Executing /lib/systemd/systemd-sysv-install disable lirc
> insserv: warning: current start runlevel(s) (empty) of script `lirc'
> overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script
> `lirc' overrides LSB defaults (0 1 6).
> allen at MythNew:/etc$
>
> I have no idea what all this means. I took out the killall lircd statement
> and tested the remote. It did not work.
>
> I put the killall back in rc.local and still no remote
>
> I issued the other command you gave  sudo systemctl start lirc and still
> no remote
>
> Also, irw is no longer recognized so I now have no remote at all.  My wife
> will be very unhappy.
>
> Pleas help me get back to where I was. I will never complain about my
> kludge again.
>
>
>
> On Tue, Aug 21, 2018 at 9:16 AM, Stephen Worthington <
> stephen_agent at jsw.gen.nz> wrote:
>
>> On Tue, 21 Aug 2018 08:22:58 -0700, you wrote:
>>
>> lirc in 16.04 is a quite old version (0.9.0).  The version in 18.04 is
>> 0.10.0, and its Python configuration tools are badly broken - clearly
>> no one ever tested them.  They can not find their libraries and crash
>> when run.  I believe lircd itself is fine, and if the config files can
>> be manually created it will work.  And it is rather more capable than
>> 0.9.0.  But I have not actually verified that as I have not upgraded
>> any of my running systems to 18.04.1 yet.
>>
>> So your choice of 16.04 is fortuitous - you need a working lirc, and
>> 18.04 does not have one yet.
>>
>> >Everything works but I am still not happy killing lircd before starting
>> it
>> >myself.
>> >
>> >1) I am surprised that entering the correct UDP ports in frontend setup
>> >didn't work.
>> >
>> >2) Assuming I still need to use rc.local, which I have no problem with as
>> >it works, I want to disable whatever else is starting lircd.  Perhaps it
>> is
>> >this file:
>> >
>> >Would /etc/lirc/hardward.conf be the file to edit?
>> >
>> >#Enable lircd
>> >START_LIRCD="true"
>> >
>> >#Don't start lircmd even if there seems to be a good config file
>> >#START_LIRCMD="false"
>> >
>> >Allen
>>
>> No, not in 16.04.  16.04 uses systemd to control and start things.  So
>> to disable lircd from starting at boot, you need to do this:
>>
>> sudo systemctl disable lirc
>>
>> When you want to start lircd later, the command is:
>>
>> sudo systemctl start lirc
>>
>> You do not need the sudo from rc.local.
>>
>> With systemd, using rc.local is regarded as the wrong way of doing
>> things, but there is a very steep learning curve with systemd to work
>> out the right way of doing things, and rc.local does still work.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180821/59786bd5/attachment.html>