[mythtv-users] Question about mythlcdserver

[Nicolas Krzywinski]

Am 23.03.2015, 13:00 Uhr, schrieb <mythtv-users-request at mythtv.org>:

> Message: 3
> Date: Mon, 23 Mar 2015 11:07:18 +1100
> From: Mike Holden <mikeholden99+mythtv at gmail.com>
> To: Discussion about MythTV <mythtv-users at mythtv.org>
> Subject: Re: [mythtv-users] Question about mythlcdserver
> Message-ID:
> 	<CAKfgc2K2-mAwrYAHO9gWM6Z_6wJBia9ARqGzz-YjPe6xpmo25w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>On 23 March 2015 at 09:14, Nicolas Krzywinski <myth at site7even.de> wrote:
>
>> Am 2015-03-11 13:00, schrieb mythtv-users-request at mythtv.org:
>>>
>>>
>>> On my system (fedora), mythlcdserver is started by mythfrontend, notby
>>> some external script. That way, it doesn't start too early.
>>>
>> This seems to be the case on my system as well, but there is nothing in
>> the mythfrontend start script, so it has to be within the mythfrontend.real
>> binary code?
>> Additionally I am using mythwelcome and this seems to start mythlcdserver
>> as well, as it is running at that point already.
>>
>> I "solved" (better: workarounded) the issue with the following script,
>> called from within mythfrontend starter script:
>> #!/bin/bash
>>
>> # Check port of mythlcdserver
>> foo=`netstat -l --tcp | grep 6545`
>> ret=$?
>>
>> if [ $ret = 0 ]
>>         then echo "Everything fine."
>> else
>>         # Wait for lcd symlink
>>         for i in `seq 1 120` ; do
>>                 echo "`date +'%FT%T.%N%:z'` - manage-lcd loop $i"
>>
>>                 if [ -h /dev/lcd-imon ]
>>                         then break
>>                 else
>>                         sleep .5
>>                 fi
>>         done
>>
>>         # Restart mythlcdserver
>>         killall mythlcdserver
>>         mythlcdserver > /var/log/mythtv/mythlcdserver-manual.log &
>> fi
>>
>> As I don't know whether the loop is needed, it works like that.
>>
>> The way, mythlcdserver is called, is at least ... kind of weird.
>>
>>
> Yes, it's mythfrontend that starts the mythlcdserver on my system.
>Fedora doesn't have the wrapper scripts, and I don't use mythwelcome either.
>You could probably simplify your script even more, and just have it kill
> the mythlcdserver, but not attempt to restart it. Mythfrontend will start
> it for itself.
True. Just in case I need the log, it is not bad to call it like above - I don't know why, but mythlcdserver stopped logging on my system a while ago... this complicated things additionally. :D