[mythtv] [mythtv-commits] Ticket #4381: Using a Miscellaneous Status Information (see ticket #4049) makes mythbackend segfault occasionnally...

Michael T. Dean mtdean at thirdcontact.com
Sat Jan 19 22:03:43 UTC 2008

On 01/19/2008 04:21 PM, Nicolas Riendeau wrote:
>  BTW, the small problem I mentionned in the ticket is that the output
>  of "sensors" is localized (at least the one bundled with FC8) so when
>  the locale is different from en_US.US-ASCII, what gets extracted by
>  awk (in the myth_sensors.sh script) is not exactly what we would want
>  it to be.
>  [For example, with a LANG=en_US.UTF-8 or LANG=en_US.ISO-8859-1, there
>  is no longer a space in the temperatures readings between the units
>  (which now use non us-ascii characters) and the temperature (number)
>  so what gets extracted contains the units.]
>  The workaround I used is to add an "export LANG=en_US.US-ASCII"
>  before the call to sensors so I did not have to find another way to
>  extract the info regardless of locale.

Yeah.  I realized when I wrote that example script that there were 
character set issues (same holds true of myth_upcoming_recordings.pl and 
myth_recent_recordings.pl), but I didn't have a way to test and figured 
they're a good start.

I think Otto K. recently put in a patch to fix some other shell script 
recently (and possibly some Perl scripts) and I had marked it in my mail 
client for follow-up so I could use it as a template for fixing the 
myth_sensors.sh script (and possibly the Perl ones), but unfortunately I 
lost my mythtv-commits and tickets folders due to a freak combination of 
mouse movement and clicks when I dropped the mouse connected to my 
laptop :( and I haven't attempted to find it again, yet.

If anyone out there with more knowledge of shell/Perl scripting than me 
knows how to fix them properly, patches would be much appreciated.  If I 
don't hear back from anyone, I'll probably take a look at fixing them 
next week.


More information about the mythtv-dev mailing list