Re: [vdr] PANIC: watchdog timer expired - exiting
Josce Unknown schrieb: Well if the PC clock was correct all the time I would probably not have to use the set time function :) Yes, but typically PC HW clock does not drift so much. You could use hwclock --systohc (and possibly --utc or --localtime) after letting the vdr to set the system clock. I am sure this would fix the problem. However, is this really the way it should work? The clock is four minutes off, let's PANIC? To be honest, I have seen a lot of worse PC clocks around than the one I have on my spare computer ... Josce Hi all, Josc, i would say your oppinion is correct, the real problem here is not the clock beeing off 4 Minutes, it is the way vdr changes the local clock without noticing his internal watchdog about this discontinuit in the timebase. I would call it a bug. either it should adjust the clock in steps of a few seconds like ntpd does or it should tell his own watchdog to ignore this jump in time. Christoph ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Changing location of /srv/vdr
Thanks for the tip about VDR_OPTIONS. The Fedora package did not create /srv/vdr and I didn't want to use this location anyway as I currently record tv to another location and wanted to stick with that. Excellent software by the way! Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Configuring vdr to use multiple drives/partitions for storage
I am trying to find out the best way to add additional storage to VDR 1.4.6-1 over time. Could someone on the list give some advise on how best to config vdr so that I can add additional storage over time as my needs increase? My current config is as follws /etc/default/vdr is as below; # /etc/default/vdr # # See also /usr/share/doc/README.Debian # # Change to 1 to enable vdr's init-script ENABLED=1 # Change this to 1 if you want vdr to be able to shutdown the # computer ENABLE_SHUTDOWN=0 # Options that will be passed to vdr's commandline # for example: OPTIONS=-w 15 OPTIONS=-w 30 -v /var/lib/video.00 # Set this to load only plugins with the correct patch level PLUGIN_CHECK_PATCHLEVEL=yes My video directory is at /var/lib/video and is a symlink to /var/lib/video.00 which is a symlink to a directory on a partition on one of my mounted partitions. My understanding is that if I add additional storage to my vdr system and then add a new symlink such as /var/lib/video.01 that points to this storage vdr will automatically use it when /var/lib/video.00 becomes full. Is that correct? I have looked for some documentation on how this aspect of vdr should/could be configured but have not found anything that clearly defines how this should be best achieved. Thanks in advance for any input on this :-) ___ 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
On Saturday, 9. Juneta 2007 13:09, Andrew Herron wrote: I am trying to find out the best way to add additional storage to VDR 1.4.6-1 over time. Could someone on the list give some advise on how best to config vdr so that I can add additional storage over time as my needs increase? Magic words are evms or lvm. Then you can add as many HDs you need afterward and just extend your video partition to cover whole new HD. Just remember to select right file system (I use reiserfs) and you can do extend even on-line (as hot) -- JJussi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
Josce Unknown wrote:
I am sure this would fix the problem. However, is this really the way it
should work?
The clock is four minutes off, let's PANIC?
VDR still defaults to start recordings three minutes before scheduled
time, right? I wouldn't want to rely my recordings on a clock that is
that bad.
To be honest, I have seen a lot of worse PC clocks around than the one I
have on my spare computer ...
The worst I had was on a 286, running 40s off per day. Good thing that
this is over. Today, I would count one or two minutes per month as worst
acceptable.
Back on the issue:
I've just tested this on my machine, with a small program that uses the
alarm() to sleep for 10 seconds, just as the watchdog uses alarm().
(Code is attached.)
This is a normal run:
#date ; ./alarm ; date
Sa 9. Jun 11:50:36 CEST 2007
alarm
Sa 9. Jun 11:50:46 CEST 2007
The second run, I started the program at 11:52:55, and at 11:53 I
manually changed the clock to 11:54. This is what happened:
#date ; ./alarm ; date
Sa 9. Jun 11:52:55 CEST 2007
alarm
Sa 9. Jun 11:54:04 CEST 2007
Just as I've expected: alarm() runs independent of any system clocks, it
always waits the specified time in seconds. There should be no reason to
modify the behavior of the watchdog, since alarm() doesn't care about
the calendar clock.
Btw: Even ntpd would step the clock in this case, because clock slew is
only used for time offsets of less than 128ms.
And, from the original post:
May 31 20:23:38 localhost vdr: [3413] System Time = Thu May 31 20:23:38 2007
(1180632218)
May 31 20:23:38 localhost vdr: [3413] Local Time = Thu May 31 20:19:37 2007
(1180631977)
May 31 20:21:01 localhost vdr: [3405] PANIC: watchdog timer expired - exiting!
The clock was set to 20:19:37, and the watchdog fires at 20:21:01 - 84
seconds later. There must be something different causing the watchdog to
expire.
Cheers,
Udo
#include signal.h
#include stdio.h
#include stdlib.h
#include unistd.h
static void Watchdog(int signum)
{
printf(alarm\n);
exit(1);
}
int main(int argc, char *argv[])
{
if (signal(SIGALRM, Watchdog) == SIG_IGN) signal(SIGALRM, SIG_IGN);
alarm(10);
while (true) sleep(1);
}
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] recordsshowfree
Moin, whenever you enter the recordings page via a direct key (e.g. the red key if no menu is open), you need to go back to the main menu page to know the available disk space. So I wrote a patch to show this info on the recordings page too, e.g.: Disk 95%, 4:40 (7,0 GB) free. It is for vdr 1.4.6 and you can download it at http://www.u32.de/vdr-1.4.6-recordsshowfree-0.2.diff Gruss, Walter -- Die Gedanken sind frei. Auschnahmen regelt ein Bundeschgesetz. ___ 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
I will look at evms lvm. Thanks. But I'd still like to understand how vdr's own managment of multiple video.xx directories works... Can anyone explain what my options are for using multiple video.xxdirectories? On 6/9/07, JJussi [EMAIL PROTECTED] wrote: On Saturday, 9. Juneta 2007 13:09, Andrew Herron wrote: I am trying to find out the best way to add additional storage to VDR 1.4.6-1 over time. Could someone on the list give some advise on how best to config vdr so that I can add additional storage over time as my needs increase? Magic words are evms or lvm. Then you can add as many HDs you need afterward and just extend your video partition to cover whole new HD. Just remember to select right file system (I use reiserfs) and you can do extend even on-line (as hot) -- JJussi ___ 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 to use multiple drives/partitions for storage
On 6/9/07, Udo Richter [EMAIL PROTECTED] wrote: The details about handling multiple video directories are explained in VDR's INSTALL file. Basically, if you specify -v /var/lib/video.00 on command line, VDR will automatically search for .01 and so on, and will use them all for recording. Disk usage will be split across all disks, even recordings will be split. VDR maintains a complete folder hierarchy in the .00 folder, using symbolic links to mirror files on other disks to the .00 folder. Cheers, Udo Hi Udo, I had noticed the symlinks to other files in the .00 directory - thanks for explaining the rationale behind that. 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? I have added a partition as .01 for example but only new recordings stored there are visible inside vdr's recordings menu but none of the 'old' recordings are. I guess what I should have done is add the 'old' recording's partition as .00 and the new partitions as .01 etc etc. Other than changing the order of the partitions symlinked to is there any way to correct this problem now? Many thanks. Andrew ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
VDR still defaults to start recordings three minutes before scheduled time, right? I wouldn't want to rely my recordings on a clock that is that bad. That's why I have set it to start ten minutes earlier :) The worst I had was on a 286, running 40s off per day. Good thing that this is over. Today, I would count one or two minutes per month as worst acceptable. I agree that the clock is bad, but one of the reasons I started to use VDR was because I had an extra old PC that could be put into use this way. If I have to start buying a lot of new stuff, then I might as well get a STB and complain and demand corrections when it doesn't work. Now I just complain :) May 31 20:23:38 localhost vdr: [3413] System Time = Thu May 31 20:23:38 2007 (1180632218) May 31 20:23:38 localhost vdr: [3413] Local Time = Thu May 31 20:19:37 2007 (1180631977) May 31 20:21:01 localhost vdr: [3405] PANIC: watchdog timer expired - exiting! The clock was set to 20:19:37, and the watchdog fires at 20:21:01 - 84 seconds later. There must be something different causing the watchdog to expire. OK, this is what I asked in the first mail: is it the watchdog causing the PANIC? And apparently it isn't the watchdog, but the log didn't show anything else that was causing it. I'll be going away for a month now but when I get back I'll see if I can reproduce the PANIC somehow, just to figure out what is happening. Josce ps I really hate using hotmail, the formatting is totally weird... _ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Configuring vdr-sxfe to use a single vdr backend for recordings/dvb cards
Hi again, Can someone give me some guidance on how to confgure the following; I have a central machine running vdr 1.4.6 (has all the recording storage and dvb cards) 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? Thanks in advance. Andrew ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PANIC: watchdog timer expired - exiting
On Sat, 2007-06-09 at 12:28 +0200, Udo Richter wrote:
And, from the original post:
May 31 20:23:38 localhost vdr: [3413] System Time = Thu May 31 20:23:38
2007 (1180632218)
May 31 20:23:38 localhost vdr: [3413] Local Time = Thu May 31 20:19:37 2007
(1180631977)
May 31 20:21:01 localhost vdr: [3405] PANIC: watchdog timer expired -
exiting!
Turning clock is always very bad and dangerous thing to do. It can cause
lot of other problems too, just to mention incomplete builds, duplicate
cron jobs, destroyed logs and files, incomplete backups ...
The clock was set to 20:19:37, and the watchdog fires at 20:21:01 - 84
seconds later. There must be something different causing the watchdog to
expire.
It might be even some plugin. All timeouts (cTimeMs, cCondVar,
cCondWait) use current wall clock time to set the timeout.
Example:
cCondWait c;
c.Wait(100);
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).
- Petri
--- ../../vdr-1.4.5-orig/tools.c 2007-01-02 06:18:41.0 +0200
+++ ../../vdr-1.4.5/tools.c 2007-01-02 06:14:03.0 +0200
@@ -549,6 +549,54 @@
uint64_t cTimeMs::Now(void)
{
+#if _POSIX_TIMERS 0 defined(_POSIX_MONOTONIC_CLOCK)
+ static bool initialized = false;
+ static bool monotonic = false;
+ struct timespec tp;
+
+ // initialization:
+ // check if monotonic timer is available and
+ // provides enough accurate resolution
+ if(!initialized) {
+
+ if(clock_getres(CLOCK_MONOTONIC, tp))
+esyslog(cTimeMs: clock_getres(CLOCK_MONOTONIC) failed);
+
+ else {
+dsyslog(cTimeMs: clock_gettime(CLOCK_MONOTONIC): clock resolution %d us,
+ ((int)tp.tv_nsec) / 1000);
+
+ // require at least 1 ms resolution
+ if( tp.tv_sec == 0 tp.tv_nsec = 100 ) {
+
+ if(clock_gettime(CLOCK_MONOTONIC, tp))
+ esyslog(cTimeMs: clock_gettime(CLOCL_MONOTONIC) failed);
+
+ else {
+ dsyslog(cTimeMs: using monotonic clock);
+ monotonic = true;
+ }
+ }
+}
+
+ initialized = true;
+ }
+
+
+ if(monotonic) {
+
+ if(!clock_gettime(CLOCK_MONOTONIC, tp))
+return (uint64_t(tp.tv_sec)) * 1000 + tp.tv_nsec / 100;
+
+ esyslog(cTimeMs: clock_gettime(CLOCK_MONOTONIC) failed);
+ monotonic = false;
+ //return 0;
+ }
+
+#else
+# warning Posix monotonic clock not available
+#endif
+
struct timeval t;
if (gettimeofday(t, NULL) == 0)
return (uint64_t(t.tv_sec)) * 1000 + t.tv_usec / 1000;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
