Re: [vdr] PANIC: watchdog timer expired - exiting
On Sun, 2007-06-10 at 12:31 +0200, Clemens Kirchgatterer wrote: Petri Hintukainen [EMAIL PROTECTED] wrote: If clock is turned 2 minutes back in middle of this, the code will wait 120100 ms instead of 100ms ... Might cause some quite weird problems. I belive there's no way to change pthread_..._timedwait functions, but cTimeMs can be changed to use monotonic timers instead of gettimeofday (patch attached). just for the record, i think you have to change the Makefile to include -lrt in the LIBS for the patch to work. That's right, that part was missing from the patch :( - Petri --- ../../vdr-1.4.5-orig/Makefile 2006-09-08 00:15:09.0 +0300 +++ ../../vdr-1.4.5/Makefile 2006-12-16 21:28:19.0 +0200 @@ -17,7 +17,7 @@ LSIDIR = ./libsi MANDIR = /usr/local/man BINDIR = /usr/local/bin -LIBS = -ljpeg -lpthread -ldl -lcap +LIBS = -ljpeg -lpthread -ldl -lcap -lrt INCLUDES = PLUGINDIR= ./PLUGINS ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
Petri Hintukainen wrote: It might be even some plugin. All timeouts (cTimeMs, cCondVar, cCondWait) use current wall clock time to set the timeout. Thats not even all: There are 140 references to time(NULL) in VDR, and most of them are used for timeouts between a few seconds and some hours. Even the famous video data stream broken (causing an emergency shutdown) can be triggered by a 30-second time step. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Configuring vdr to use multiple drives/partitions for storage
Andrew Herron wrote: If I have some existing vdr recordings on another partition is there a way to include these so that they are visible inside vdr's recording's menu? You can symlink the partition into the first partition as directory. Not very clean, but should work for playback. (but be aware that VDR's delete-old-recordings strategy expects that deleting a recording /video/symlink/recording results in free space in /video, and VDR may delete everything in /video/symlink/ quickly if this is not part of any recording folder.) The alternative is to do all the linking of files manually, just as VDR would have done it. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Configuring vdr-sxfe to use a single vdr backend for recordings/dvb cards
On 6/9/07, Petri Hintukainen [EMAIL PROTECTED] wrote: On Sat, 2007-06-09 at 18:15 +0100, Andrew Herron wrote: I have several networked vdr machines that i want to use to connect back to the 'server' vdr machine. The networked vdr machines will have no dvb cards (they will all be located at the vdr server). How do i configure my vdr client machines to connect back to the server vdr machine and use its dvb cards/recording storage etc? Can anyone give some guidance on this type of setup or point me at a url where I can find out about such a config? If you don't watch different recordings / channels at the same time you can just run vdr-sxfe at each client and connect to the single VDR server. You'll get same video + OSD mirrored to all locations. But, if you need to have independently controlled clients with own video and OSD, you need to run several instances of VDR - it doesn't matter if you run all VDR instances on server or at each client. I run several VDR instances on the server: - less maintenance, only one installation of VDR and plugins required - allows using diskless clients (and with less memory) - Faster cutting / DVD burning / ... as there is no network between VDR and disks - no need to export/mount /video to every client - ... Here's how I do it: master VDR: DVB cards, recordings, server for client 1: vdr -c /etc/vdr \ -Pxineliboutput --local=none --remote=37890 \ -Pstreamdev-server server for client 2: vdr -c /etc/vdr2 \ -D 10 \ -Pxineliboutput --local=none --remote=37892 \ -Pstreamdev-client server for client 3: vdr -c /etc/vdr3 \ -D 10 \ -Pxineliboutput --local=none --remote=37894 \ -Pstreamdev-client + other options / plugins you normally use. Using -D 10 option for client VDR instances forces all DVB cards for master VDR. Streamdev plugin is used to provide live view for client VDR's, it is not required to just watch recordings. You must use separate configuration directory for each VDR (-c option). Without it you'll most likely break all recordings (all VDRs record all timers in paraller to same recording directory). And at clients: Client 1: vdr-sxfe Client 2: vdr-sxfe xvdr://server ip:37892 Client 3: vdr-sxfe xvdr://server ip:37894 If you use RTP between vdr and vdr-sxfe, using separate RTP address or port for each xineliboutput server instance might be good idea. Also it might be good idea to disable recording at all but the master vdr. Recording the same timer on two VDR instances will most likely corrupt whole recording. Besides that, doing all recordings directly from DVB card (no streamdev in middle) makes things simpler and less error prone. It is probably even impossible to do several recordings from different transponders using single streamdev instance. I use timersync plugin to disables recording on client VDRs. All timers are still visible at each client and you can create/modify timers at any client just as before. Plugin synchronizes all modifications to timers between VDR instances and takes care that all recordings are made only by master vdr. Still, if you have some kind of autotimer plugins etc. that generate timers automatically it might be better to run those only at server vdr... - Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Petri, I have few questions after testing your suggestions above to achieve independently controlled clients with their own video and OSD; I would like all recordings to be managed/controlled by the master vdr as this would seem to be the best solution. However if I have say a single twin tuner DVB-T card and the master vdr is controlling all recordings is it still possible for the remote clients to schedule a recording via the master vdr if the timersync plugin is used? I think that you are saying this is possible... which is great! I have created separate /etc/vdr2 /etc/vdr3 directories by copying /etc/vdr Will this work ok? As both /etc/vdr3 /etc/vdr3 are exact copies of /etc/vdr without any changes in the conf files etc. Is this what you meant or do i need to make any changes in /etc/vdr3 /etc/vdr3 ? Cheers Andrew ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] VDR developer version 1.5.3
VDR developer version 1.5.3 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.2-1.5.3.diff This version finally brings UTF-8 capability to VDR! There are still a few minor details to iron out, but all in all it already works pretty good. Note that if you run VDR on a UTF-8 system, it will write all its text files using UTF-8. Existing text files written in ISO will not be automatically converted to UTF-8. You will need to do this yourself if necessary. Channel and EPG data will be automatically changed to UTF-8 as new data comes in. If you run VDR on a system with ISO character set, files will still be stored in ISO just as before. Several bugfixes etc. that have been posted on the mailing list lately are still in my inbox and I have yet to look into them. WARNING: This is a *developer* version. Even though *I* use it in my productive environment, I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 1.5.2: - Fixed some spelling errors in 'newplugin' (thanks to Ville Skyttä). - Fixed a busy loop in fast forward if the next video data file is missing (thanks to Reinhard Nissl). - Fixed handling frequencies in NitFilter::Process() (thanks to Anssi Hannula). - Fixed a race condition with signal handlers at program exit (thanks to Udo Richter). - Non-primary devices in Transfer mode are now also used for recording (thanks to Anssi Hannula). - Fixed handling ChannelUp/Down keys if there is currently a replay running (thanks to Marco Schlüßler). - The new SVDRP command REMO can be used to turn VDR's remote control off and on in case other programs need to be controlled (based on patches from Krzysztof Parma and Helmut Auer). - Increased the maximum number of CA system ids to cope with the AlphaCrypt CAM's version 3.11 firmware. - Fixed getting the code setting from the locale (thanks to Matthias Schwarzott). - Implemented support for Freetype fonts (based on a patch from Alexander Riedel). The font names and sizes can be adjusted in the Setup/OSD menu. Note that VDR now requires freetype fonts to be installed in /usr/share/fonts/truetype. - If the OSD device in use has at least 8bpp bitmap depth and this is also used by the current skin, Freetype fonts are displayed anti-aliased. The new setup parameter OSD/Anti-alias can be used to turn this off. - The new function cOsd::SetAntiAliasGranularity() can be used to help the OSD in managing the available color palette entries when doing anti-aliasing. Skins that use 8bpp bitmaps can call this function with the maximum number of colors used, and the maximum number of color combinations. The OSD will then evenly split the available palette entries between the various colors combinations, so that fonts can be anti-aliased. By default a total of 10 colors and 10 combinations is assumed. - The pixel fonts have been completely removed from the VDR source. - VDR is now UTF-8 aware. It handles strings according to the character encoding used on the user's system. All internationalization strings and incoming SI data are converted to the system encoding. - Plugins that handle strings need to be aware that on systems with UTF-8 encoding a character symbol may consist of more than a single byte in memory. The functions and macros named Utf8...() can be used to handle strings without needing to care about the underlying character encoding (see tools.h for details). - Even though the weekdays of repeating timers are presented to the user as UTF-8 characters in the OSD, the timers.conf file and the SVDRP timer commands still use single byte characters (MTWTFSS) to make sure this information is handled correctly between systems with different character encodings. - Added a missing i18n string for CAM in the Turkish OSD texts. - Improved editing strings that are too long to fit into the editable area. - Changes to the OSD settings in the Setup/OSD menu now immediately take effect when the Ok key is pressed. Have fun! Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Configuring vdr to use multiple drives/partitions for storage
Udo - thanks for that. Much appreciated. On 6/10/07, Udo Richter [EMAIL PROTECTED] wrote: Andrew Herron wrote: If I have some existing vdr recordings on another partition is there a way to include these so that they are visible inside vdr's recording's menu? You can symlink the partition into the first partition as directory. Not very clean, but should work for playback. (but be aware that VDR's delete-old-recordings strategy expects that deleting a recording /video/symlink/recording results in free space in /video, and VDR may delete everything in /video/symlink/ quickly if this is not part of any recording folder.) The alternative is to do all the linking of files manually, just as VDR would have done it. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Configuring vdr-sxfe to use a single vdr backend for recordings/dvb cards
On Sun, 2007-06-10 at 14:15 +0100, Andrew Herron wrote: I would like all recordings to be managed/controlled by the master vdr as this would seem to be the best solution. However if I have say a single twin tuner DVB-T card and the master vdr is controlling all recordings is it still possible for the remote clients to schedule a recording via the master vdr if the timersync plugin is used? I think that you are saying this is possible... which is great! Ÿes. All timer stuff works just as when using single VDR - if you set a timer at any client, it is immediately transferred to server (and visible to all other clients too). Plugin monitors timers state and synchronices all timer changes between VDR instances. Only master vdr does recordings, recording is completely disabled at all client VDRs (there's no way to record anything on client VDR even if one wants to). There's one restriction: With timersync you can't (at least yet) modify timers that are currently recording - such timers can be modified only at master VDR. I have created separate /etc/vdr2 /etc/vdr3 directories by copying /etc/vdr Will this work ok? Yes. Maybe you need to configure streamdev server address (127.0.0.1) for clients, but you can do that from client setup menu when you have client running. Be sure to empty all client VDR timers.conf files, if timersync refuses to load etc. you might end up having N*3 recordings running immediately at startup :) One more thing: using suspendoutput plugin with some proper timeout value in every VDR instance might be good idea - it releases streamdev VTP connection and server-side DVB devices for other use when the client is not in use. - Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3
Hi, On Sun, 2007-06-10 at 15:45 +0200, Klaus Schmidinger wrote: VDR developer version 1.5.3 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.2-1.5.3.diff - The pixel fonts have been completely removed from the VDR source. - VDR is now UTF-8 aware. It handles strings according to the character encoding used on the user's system. All internationalization strings and incoming SI data are converted to the system encoding. nice to hear this. I'm beginning with 1st plugin, that can't this handle. and it's your plugin :-) make[1]: Entering directory `/tmp/vdr-1.5.3/PLUGINS/src/skincurses' g++ -fPIC -g -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='skincurses' -I../../../include skincurses.c ../../../include/vdr/font.h:36: warning: ‘virtual int cFont::Width(uint) const’ was hidden skincurses.c:24: warning: by ‘cCursesFont::Width’ skincurses.c: In constructor ‘cCursesFont::cCursesFont()’: skincurses.c:22: error: no matching function for call to ‘cFont::cFont(NULL)’ ../../../include/vdr/font.h:31: note: candidates are: cFont::cFont() ../../../include/vdr/font.h:31: note: cFont::cFont(const cFont)skincurses.c: At global scope: skincurses.c:30: error: cannot declare variable ‘Font’ to be of abstract type ‘const cCursesFont’ skincurses.c:20: note: because the following virtual functions are pure within ‘const cCursesFont’: ../../../include/vdr/font.h:36: note: virtual int cFont::Width(uint) const ../../../include/vdr/font.h:44: note: virtual void cFont::DrawText(cBitmap*, int, int, const char*, tColor, tColor, int) const make[1]: *** [skincurses.o] Error 1 Regards Oleg Roitburd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
On Sun, 2007-06-10 at 14:59 +0200, Udo Richter wrote:
Petri Hintukainen wrote:
It might be even some plugin. All timeouts (cTimeMs, cCondVar,
cCondWait) use current wall clock time to set the timeout.
Thats not even all: There are 140 references to time(NULL) in VDR, and
most of them are used for timeouts between a few seconds and some hours.
Even the famous video data stream broken (causing an emergency
shutdown) can be triggered by a 30-second time step.
He :)
All places where time(NULL) is used to measure some time interval could
easily be changed to use monotonic cTimeMs.
But with timers current wall clock time is really required ...
It might be enough to replace most of time(NULL) 's with something like
time_t cTimeMs::Time(void) {
return (time_t)(cTimeMs::Now() / 1000);
}
Using the cTimeMs timer/trigger mechanism requires some more changes and
debugging.
- Petri
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3
On 06/10/07 16:32, Oleg Roitburd wrote: Hi, On Sun, 2007-06-10 at 15:45 +0200, Klaus Schmidinger wrote: VDR developer version 1.5.3 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.3.tar.bz2 A 'diff' against the previous developer version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.2-1.5.3.diff - The pixel fonts have been completely removed from the VDR source. - VDR is now UTF-8 aware. It handles strings according to the character encoding used on the user's system. All internationalization strings and incoming SI data are converted to the system encoding. nice to hear this. I'm beginning with 1st plugin, that can't this handle. and it's your plugin :-) make[1]: Entering directory `/tmp/vdr-1.5.3/PLUGINS/src/skincurses' ... Well, this is one of the things I referred to by There are still a few minor details to iron out ;-). I haven't looked at any of the plugins yet - I wanted to get the core program up and running first. Maybe you should try the core program by itself first. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] pvr350-Plugin -new development snapshot
I just announced it in the vdrportal forum, but it may also be interesting for non-german speaking vdr users. The pvr350-plugin implements an output device for the PVR350 TV out, using the hardware mpeg2 decoder. It was originally written by Dominic Morris, but he stopped development. Based on the last version 0.0.5 from December 2005 (which was only sent to a few people), I adapted the plugin during the last 18 months to ivtv changes. Although I have only very limited knowledge about C++, I also managed to improve some things. Andreas Schäfers helped me a lot; he introduced even ac3-to-mp2 conversion which is important if you use the dvd-plugin. Look into the README for requirements and further details. http://drseltsam.device.name/vdr/pvr/src/pvr350/ There is still much work to do - feel free to contribute patches! For watching analogue TV from the tuner of the PVR350 you need a second plugin as input device. Because the analogtv-plugin is out of date, I highly recommend the latest unofficial pvrinput. Have a look at http://drseltsam.device.name/vdr/pvr/src/pvrinput/vdr-pvrinput-1.0.0_20070523.tgz or http://free.pages.at/wirbel4vdr/unofficial_stuff/vdr-pvrinput-1.0.0_20070523.tgz and look into the README. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3
Klaus Schmidinger wrote: - Implemented support for Freetype fonts (based on a patch from Alexander Riedel). The font names and sizes can be adjusted in the Setup/OSD menu. Note that VDR now requires freetype fonts to be installed in /usr/share/fonts/truetype. In my system there is no /usr/share/fonts/truetype, but the TTF fonts reside in other subdirectories under /usr/share/fonts. + strcpy(FontOsd, arialbd.ttf); + strcpy(FontSml, arial.ttf); + strcpy(FontFix, courbd.ttf); I'd use some free-as-in-freedom font (Vera?) by default, that are more likely installed in systems. Alternatively, you could use the fontconfig library [1] for managing fonts. This would also allow using using the system default fonts via aliases like 'sans-serif' etc, and using a font list instead of having to manually write the font filename via OSD. You can get a quick idea from looking at the patch which added fontconfig support for mplayer [2], though of course you should look in fontconfig documentation instead of copying conventions from mplayer :) [1] http://fontconfig.org/ [2] http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/2003-November/022218.html -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3
On 06/10/07 17:53, Anssi Hannula wrote: Klaus Schmidinger wrote: - Implemented support for Freetype fonts (based on a patch from Alexander Riedel). The font names and sizes can be adjusted in the Setup/OSD menu. Note that VDR now requires freetype fonts to be installed in /usr/share/fonts/truetype. In my system there is no /usr/share/fonts/truetype, but the TTF fonts reside in other subdirectories under /usr/share/fonts. Well, it's a real pitty with the various systems putting files at random places. Can't there be a *standard* for things like this? + strcpy(FontOsd, arialbd.ttf); + strcpy(FontSml, arial.ttf); + strcpy(FontFix, courbd.ttf); I'd use some free-as-in-freedom font (Vera?) by default, that are more likely installed in systems. Those were the ones suggested in Alexander Riedel's original patch. Which ones would you suggest? Alternatively, you could use the fontconfig library [1] for managing fonts. This would also allow using using the system default fonts via aliases like 'sans-serif' etc, and using a font list instead of having to manually write the font filename via OSD. You don't have to manually write the font name. This is a list of strings that contains all the file names found in /usr/share/fonts/truetype (or wherever your system my have these files - I guess this will have to become a compile-time switch - sigh). Just use the Left/Right keys to navigate through it. You can get a quick idea from looking at the patch which added fontconfig support for mplayer [2], though of course you should look in fontconfig documentation instead of copying conventions from mplayer :) [1] http://fontconfig.org/ [2] http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/2003-November/022218.html I'd like to keep it simple. There's a directory with font file names and these will be offered in Setup/OSD. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3
On Sun, 10 Jun 2007, Klaus Schmidinger wrote: Well, it's a real pitty with the various systems putting files at random places. How about setting the FONTDIR configurable through Make.config or ever commandline switch? On my first test run of vdr-1.5.3 it kept crashing without hinting that no font files could be found. It would be very convenient to inform users that the required fonts are missing rather than doing segmentation fault :) BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.3
On Sun, 2007-06-10 at 18:04 +0200, Klaus Schmidinger wrote: On 06/10/07 17:53, Anssi Hannula wrote: Klaus Schmidinger wrote: Can't there be a *standard* for things like this? + strcpy(FontOsd, arialbd.ttf); + strcpy(FontSml, arial.ttf); + strcpy(FontFix, courbd.ttf); I'd use some free-as-in-freedom font (Vera?) by default, that are more likely installed in systems. Bitstream Vera isn't good enough...it doesn't provide Cyrillic part of UTF-8 :-( M$ fonts are not free. My suggestion is liberation ttf from RedHat https://www.redhat.com/promo/fonts/ Regards Oleg Roitburd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.3 - LANG=[EMAIL PROTECTED] not recognized
Joachim Wilke wrote: Hi everbody, in my system the LANG environment is set to [EMAIL PROTECTED]. VDR did not recognize this character set. After I changed LANG to de_DE.iso-8859-15 umlauts are correctly displayed e.g.in the EPG data. But I still get the following error in syslog: codeset is 'ISO-8859-15' - unknown. What's wrong here? I had a look into vdr.c and found out, that the dot is used delimiter between language and codeset - as [EMAIL PROTECTED] does not contain any dot, vdr fails to recognize this. Is [EMAIL PROTECTED] an invalid value for this variable? It is not. locale -a prints all the installed locales, and any of those values is valid for you to use. I didn't find any info via quick search, but I believe that instead of parsing the localename, VDR should use some external function to get the language/charset of the current locale. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR exited with status 134
Most of the time when VDR shuts the box down using vdrshutdown script there is a line in the log runvdr: VDR exited with status 134, attempting restart I've got fedora with runvdr from fedora vdr package and it tries to restart VDR if exit code is something else than 0, 2 or 137. Sometimes the exit code is 137 but most of the time it is 134. This causes VDR to restart (or runvdr makes VDR to restart) and dvb drivers to reload. What does exit code 134 mean? Why is exit code sometimes 137 and most of the times 134? What should exit code be when VDR is shutting down either because the user pushed power button or because there has been no user activity? I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some plugins not in fedora packaging). \\Kartsa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.3 - issue with translations out of plugins
On 06/10/07 21:43, Joachim Wilke wrote: Hi Klaus, I just installed vdr-1.5.3, but lcdproc plugin caused vdr to crash on startup. I figured out that the problem is the translation of the string Volume . Unlike the other strings that are used by the plugin this string is provided by the vdr-core i18n.c This worked fine in vdr-1.5.1. Adding a dummy translation of Volume directly in the plugins i18n.c fixed the crash. Is this the intended behaviour? Or was this a feature by accident? ;-) This was certainly unintended. I'll look into it. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.3 - LANG=[EMAIL PROTECTED] not recognized
Klaus Schmidinger wrote: On 06/10/07 22:22, Anssi Hannula wrote: Joachim Wilke wrote: I had a look into vdr.c and found out, that the dot is used delimiter between language and codeset - as [EMAIL PROTECTED] does not contain any dot, vdr fails to recognize this. Is [EMAIL PROTECTED] an invalid value for this variable? It is not. locale -a prints all the installed locales, and any of those values is valid for you to use. I didn't find any info via quick search, but I believe that instead of parsing the localename, VDR should use some external function to get the language/charset of the current locale. There's getenv(LANG), setlocale(LC_CTYPE, ), and Thomas Günther recently suggested in a PM to use nl_langinfo(CODESET). Quite a few options - which one is the right one? ;-) Somebody with insight please advise exactly how to do this - I personally just set LANG to de_DE.iso8859-1 and live happily ever after ;-) Looking at nl_langinfo manpage, it seems to me that nl_langinfo(CODESET) is the correct one to use: Return a string with the name of the character encoding used in the selected locale, such as UTF-8, ISO-8859-1, or ANSI_X3.4-1968 (better known as US-ASCII). This is the same string that you get with locale charmap. For a list of charac- ter encoding names, try locale -m, cf. locale(1). -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR exited with status 134
On Sunday 10 June 2007, Kartsa wrote: I've got fedora with runvdr from fedora vdr package and it tries to restart VDR if exit code is something else than 0, 2 or 137. Sometimes the exit code is 137 but most of the time it is 134. This causes VDR to restart (or runvdr makes VDR to restart) and dvb drivers to reload. What does exit code 134 mean? From man bash: The return value of a simple command is its exit status, or 128+n if the command is terminated by signal n. So 134 - 128 = 6, SIGABRT (kill -l 6). info SIGABRT says: This signal indicates an error detected by the program itself and reported by calling `abort'. Why is exit code sometimes 137 and most of the times 134? It's 137 when killproc (see /etc/init.d/functions) invoked from /etc/init.d/vdr gets tired of waiting for kill -TERM to result in vdr to shut down and issues a kill -KILL to really get rid of it. It's 134 when you got a crash caused by SIGABRT. If you wish to debug it further, uncomment DAEMON_COREFILE_LIMIT=unlimited at end of /etc/sysconfig/vdr and watch if core dumps start to appear in /tmp. What should exit code be when VDR is shutting down either because the user pushed power button or because there has been no user activity? 0 if all went well (and if I remember correctly). I've replaced fedoras VDR with my own vdr-1.4.6 compilation (due to some plugins not in fedora packaging). In my experience, crashes at vdr shutdown are almost always caused by plugin bugs. I'm not aware of any such in the Fedora plugin packages at the moment. By the way, which packaged plugins are you missing/adding? The last crash-at-shutdown bug I saw was in ttxtsubs; in case you're using it, my patch for the crash is included in Rofa's kermanekka edition (http://www.saunalahti.fi/~rahrenbe/vdr/patches/, Fedora 7 packages at http://cachalot.mine.nu/ and possibly sometime soonish in Fedora proper). Also, just in case you weren't aware of it, if your additional plugins don't require patching vdr itself (patches for subtitles and ttxtsubs plugins are already included), you can use Fedora's vdr and vdr-devel packages and build additional plugins for it instead of building a whole vdr of your own, see /usr/share/doc/vdr-*/README.package ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.3 - LANG=[EMAIL PROTECTED] not recognized
On Sonntag, 10. Juni 2007, Klaus Schmidinger wrote: On 06/10/07 22:22, Anssi Hannula wrote: [...] I didn't find any info via quick search, but I believe that instead of parsing the localename, VDR should use some external function to get the language/charset of the current locale. There's getenv(LANG), setlocale(LC_CTYPE, ), and Thomas Günther recently suggested in a PM to use nl_langinfo(CODESET). Quite a few options - which one is the right one? ;-) I would also use nl_langinfo(CODESET), as Anssi said. getenv(LANG) is probably to coarse and the old way of doing things, nl_langinfo is the modern way. setlocale(LC_CTYPE, ) sets the locale to nothing -- what you probably meant is setlocale(LC_CTYPE, 0) ... just to clarify things, in case somebody wants to use the knowledge of these emails later :-) Kind regards, Stefan ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
