[mythtv-users] mythtv/master commit: 6ffb557d6 by Raymond Wagner (wagnerrp)

[Robert McNamara]

2011/7/12 Warpme <warpme at o2.pl>:
>>The original message complained about strange behavior when querying
>>location. The location during playback will display the title and subtitle
>>of the show being played back, which depending on location may very well
>>include UTF-8 text. Telnet is an ASCII protocol, and telnet clients cannot
>>handle UTF-8 text. Any properly behaving telnet client will interpret ASCII
>>(>127) characters as control codes, and react accordingly. Similarly, any
>>properly behaving telnet client will send various control codes which will
>>be interpreted to the control socket as text, and cause unpredictable
>>behavior.
>
> Oh well - one thing:
> Issue described in OP has direct correlation with mentioned commit.
> Reverting this commit removes described issues on exactly the same
> environment (I mean i.e. played content).
> I'm using mentioned perl script since 2y in production environment and
> during those 2y there was no situation when telnet access causes seg in fe.
>
> I really appreciate help suggestions about switching from telnet to nc.
> Unfortunately I prefer problem solution over workaround (I mean reverting
> commit instead of removing telenet access).

You're not being offered a workaround-- The frontend control socket is
not a telnet socket-- we've been telling people for years that using
telnet with it can and will cause crashes.  Just because you avoided
them until now doesn't mean we need to make changes to support what we
have always said is a broken way to access the socket.  You need to
stop using telnet-- it is not, and never will be, a supported means of
accessing the control socket.

Fix your script.

Robert