AW: [vdr] Wakeup On LAN
Well :) .. you've got a solution .. maybe a "normal" board would have also solved the problems. Have you checked S4 regarding Power consumption? How much power is drained? 20W standby translates into 30€ a year .. Martin -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Bernd Juraschek Gesendet: Sonntag, 4. März 2007 22:04 An: vdr@linuxtv.org Betreff: Re: [vdr] Wakeup On LAN Hi, > Regarding waking up at a certain time: > Go to the wiki in read carefully about nvram-wakeup. This damn Siemens D1605 board is not supported by nvram-wakeup. First Siemens has some own checksum calculation and second guess-helper isn't able to guess the CMOS addresses for the alarm clock. Thinking about using ACPI wakeup, cat /proc/acpi/alarm tells me "2007-03-00 19:03:00" with 00 for the day - regardless of the value written into. But - I've not tested this with S4 mode. Alarm wakeup is not urgent for me because I use my router to wakeup the PC the right time. The PC safes the time into the router before it hibernats. The router uses this time to wakeup the PC per WOL. Greetings, Bernd ___ 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] Wakeup On LAN
Hi, > Regarding waking up at a certain time: > Go to the wiki in read carefully about nvram-wakeup. This damn Siemens D1605 board is not supported by nvram-wakeup. First Siemens has some own checksum calculation and second guess-helper isn't able to guess the CMOS addresses for the alarm clock. Thinking about using ACPI wakeup, cat /proc/acpi/alarm tells me "2007-03-00 19:03:00" with 00 for the day - regardless of the value written into. But - I've not tested this with S4 mode. Alarm wakeup is not urgent for me because I use my router to wakeup the PC the right time. The PC safes the time into the router before it hibernats. The router uses this time to wakeup the PC per WOL. Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.1 & problems with the new shutdown code
Udo Richter wrote: > Rolf Ahrenberg wrote: >> On Sun, 4 Mar 2007, Udo Richter wrote: >> Mar 4 18:31:14 xxx vdr: [6740] LastActivity: Never >> Mar 4 18:31:14 xxx vdr: [6740] ActiveTimeout: 2104 >> Mar 4 18:31:14 xxx vdr: [6740] Retry: Never >> >> ... goes on and on and no shutdown attempts... > > Found it! And, more important: Blame Klaus! :) It's always good to have somebody to blame ;-) Especially with such an important feature... Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup On LAN
Bernd Juraschek schrieb: Hi! Now I've patched my kernel with suspend2. Now after hibernating to suspend-to-ram or ACPI S4 WOL is working perfectly. Hibernating to the poweroff mode disables WOL again. Is WOL never possible if the PC is soft powered off? After powering off the PC per long-pressing the power button WOL works perfectly. The normal shutdown seems to disable wakeup :-( You might want to try google ;) Assuming from your mail that you speak german also (even if not, it should give you pointers), this might help: http://de.gentoo-wiki.com/Wake_On_Lan Looks like the key points are: - you need to switch on WOL on the network card with ethtool (most probably everytime you shut down. (On Gentoo according to the Howto: Edit /etc/conf.d/local.stop like below: # /etc/conf.d/local.stop # This is a good place to unload any misc. # programs you started above. # For example, if you are using OSS and have # "/usr/local/bin/soundon" above, put # "/usr/local/bin/soundoff" here. /usr/sbin/ethtool -s eth0 wol g ) - you need to make sure the net interface is not switched off during shutdown. (On Gentoo : You have to edit /etc/conf.d/rc like below: # RC_DOWN_INTERFACE allows you to specify if RC will bring the interface # compeletly down when it stops. The default is yes, but there are some # instances where you may not want this to happen such as using Wake On LAN. RC_DOWN_INTERFACE="no" ) Looks reasonable from what ihave read until now :) BTW: Thats the search i have done http://www.google.de/search?q=wake+on+lan+gentoo&start=0&ie=utf-8&oe=utf-8&meta=lr%3Dlang_de&client=firefox-a&rls=org.mozilla:de:official ;) HTH Steffen ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wakeup On LAN
Hi, it seems to be a problem with the Siemens D1605 board. WOL isn't working for ACPI S3 sleep mode. After Changing to S4 all is fine. But - I think yesterday it was working with S3 also. I will try it again after all recordings are done ... Greetings, Bernd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Re: VDR shutdown when timer gets no video
VDR 1.4.5 seems to shut down when a timer is triggered and no video is recieved. This happens when the dish is moving or CA keys are out of date. FELOCK is not enough to stop the shut down. Is there some way to turn off this feature? Actually turn off auto shut down all together? Thanks, mark ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR shutdown when timer gets no video
VDR 1.4.5 seems to shut down when a timer is triggered and no video is recieved. This happens when the dish is moving or CA keys are out of date. FELOCK is not enough to stop the shut down. Is there some way to turn off this feature? Actually turn off auto shut down all together? Thanks, mark ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
AW: [vdr] Wakeup On LAN
Regarding waking up at a certain time: Go to the wiki in read carefully about nvram-wakeup. Keep also in mind that there are broken bioses around - you need to reboot to put an alarm active. I also have this with my Asus board. Can be done with: echo -e "savedefault --default=3 --once\nquit" | grub --batch /etc/grub/menu.lst default saved .. ### END DEBIAN AUTOMAGIC KERNELS LIST title=Power off root(hd0,0) savedefault 0 halt Martin -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Bernd Juraschek Gesendet: Samstag, 3. März 2007 16:22 An: vdr@linuxtv.org Betreff: Re: [vdr] Wakeup On LAN Hi, Another problem: I would like to use alarm ACPI wakeup for booting the PC before the next recording starts. I've not tried this with hibernate, but with poweroff this also doesn't work. Is this the same problem? Some strange effect is also: --- # echo "2007-03-03 12:00:00" > /proc/acpi/alarm # cat /proc/acpi/alarm 2007-03-00 12:00:00 # --- Thanks for another idea, Bernd ___ 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
AW: [vdr] Wakeup On LAN
Linux usually shuts down all interfaces, when going down (init 0) .. On Ubuntu it's in: /etc/init.d/networking -> it does an "ifconfig eth0 down" Then WOL then will never work, since the LAN-port is without power. You may check for: [EMAIL PROTECTED]:/etc$ ll rc?.d |grep network lrwxrwxrwx 1 root root 20 2006-06-07 20:45 S35networking -> ../init.d/networking lrwxrwxrwx 1 root root 20 2006-06-07 20:45 S35networking -> ../init.d/networking lrwxrwxrwx 1 root root 20 2006-06-07 20:45 S40networking -> ../init.d/networking Try this: go into single user mode with "init 1" - check, if there is still power at your network port. If not, your LAN is shut down. Martin -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Bernd Juraschek Gesendet: Samstag, 3. März 2007 18:53 An: vdr@linuxtv.org Betreff: Re: [vdr] Wakeup On LAN Hi! > Now I've patched my kernel with suspend2. Now after hibernating to > suspend-to-ram or ACPI S4 WOL is working perfectly. Hibernating to > the poweroff mode disables WOL again. Is WOL never possible if the > PC is soft powered off? After powering off the PC per long-pressing the power button WOL works perfectly. The normal shutdown seems to disable wakeup :-( Greetings, Bernd ___ 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] [RFC] Shutdown rewrite for 1.5.x
Hi list, In the 'final' 1.0 version of the shutdown patch, and in VDR 1.5.1, a small bug slipped through that prevented automatic shutdown after VDR started for a recording only. I've uploaded a new 1.1 version of the patches for VDR 1.4.5, VDR 1.5.0 and VDR 1.5.1 to my web page: http://www.udo-richter.de/vdr/patches.html#shutdown http://www.udo-richter.de/vdr/patches.en.html#shutdown The minimal patch for 1.5.1 should also work on the shutdown-1.0-patched VDR 1.4.5/1.5.0 versions, and doesn't require plugins to be recompiled. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.1 & problems with the new shutdown code
On Sun, Mar 04, 2007 at 08:31:16PM +0100, Udo Richter wrote: > Rolf Ahrenberg wrote: > >On Sun, 4 Mar 2007, Udo Richter wrote: > >Mar 4 18:31:14 xxx vdr: [6740] LastActivity: Never > >Mar 4 18:31:14 xxx vdr: [6740] ActiveTimeout: 2104 > >Mar 4 18:31:14 xxx vdr: [6740] Retry: Never > > > >... goes on and on and no shutdown attempts... > > Found it! And, more important: Blame Klaus! :) > > Klaus changed the meaning of cRemote::LastActivity() before integrating > it, and missed to adapt one call to it, the cRemote::LastActivity() > > ACTIVITYTIMEOUT check before doing housekeeping. And after startup, > cRemote::LastActivity() will return 0, blocking all housekeeping. > Correct is (time(NULL) - cRemote::LastActivity()) > ACTIVITYTIMEOUT, as > in the attached patch. That explains why I haven't had any problems with this, with any version of your shutdown rewrite patch for vdr 1.4. It's good to use the stable version. :-) Marko ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.1 & problems with the new shutdown code
Rolf Ahrenberg wrote:
On Sun, 4 Mar 2007, Udo Richter wrote:
Mar 4 18:31:14 xxx vdr: [6740] LastActivity: Never
Mar 4 18:31:14 xxx vdr: [6740] ActiveTimeout: 2104
Mar 4 18:31:14 xxx vdr: [6740] Retry: Never
... goes on and on and no shutdown attempts...
Found it! And, more important: Blame Klaus! :)
Klaus changed the meaning of cRemote::LastActivity() before integrating
it, and missed to adapt one call to it, the cRemote::LastActivity() >
ACTIVITYTIMEOUT check before doing housekeeping. And after startup,
cRemote::LastActivity() will return 0, blocking all housekeeping.
Correct is (time(NULL) - cRemote::LastActivity()) > ACTIVITYTIMEOUT, as
in the attached patch.
Cheers,
Udo
Index: vdr.c
===
--- vdr.c (Revision 874)
+++ vdr.c (Arbeitskopie)
@@ -1162,7 +1162,7 @@
ShutdownHandler.countdown.Cancel();
}
-if (!Interact && !cRecordControls::Active() && !cCutter::Active() &&
!Interface->HasSVDRPConnection() && cRemote::LastActivity() > ACTIVITYTIMEOUT) {
+if (!Interact && !cRecordControls::Active() && !cCutter::Active() &&
!Interface->HasSVDRPConnection() && (time(NULL) - cRemote::LastActivity()) >
ACTIVITYTIMEOUT) {
// Handle housekeeping tasks
// Shutdown:
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.1 & problems with the new shutdown code
On Sun, 4 Mar 2007, Udo Richter wrote: Please add the attached patch, it logs some more infos that might shed light on this. Ok. Here's my log debug entries: Mar 4 17:56:06 xxx vdr: [6740] VDR version 1.5.1 started Mar 4 17:56:10 xxx vdr: [6740] Manual Start check: Delta = 230 Mar 4 17:57:14 xxx vdr: [6740] LastActivity: Never Mar 4 17:57:14 xxx vdr: [6740] ActiveTimeout: 64 Mar 4 17:57:14 xxx vdr: [6740] Retry: Never ... Mar 4 17:59:14 xxx vdr: [6740] LastActivity: Never Mar 4 17:59:14 xxx vdr: [6740] ActiveTimeout:184 Mar 4 17:59:14 xxx vdr: [6740] Retry: Never Mar 4 18:00:00 xxx vdr: [6740] timer 14 (3 1800-1805 'zzz') start Mar 4 18:00:14 xxx vdr: [6740] LastActivity: Never Mar 4 18:00:14 xxx vdr: [6740] ActiveTimeout:244 Mar 4 18:00:14 xxx vdr: [6740] Retry: Never ... Mar 4 18:04:14 xxx vdr: [6740] LastActivity: Never Mar 4 18:04:14 xxx vdr: [6740] ActiveTimeout:484 Mar 4 18:04:14 xxx vdr: [6740] Retry: Never Mar 4 18:05:01 xxx vdr: [6740] timer 14 (3 1800-1805 'zzz') stop Mar 4 18:05:14 xxx vdr: [6740] LastActivity: Never Mar 4 18:05:14 xxx vdr: [6740] ActiveTimeout:544 Mar 4 18:05:14 xxx vdr: [6740] Retry: Never Mar 4 18:06:13 xxx vdr: [6740] deleting timer 14 (3 1800-1805 'zzz') Mar 4 18:06:14 xxx vdr: [6740] LastActivity: Never Mar 4 18:06:14 xxx vdr: [6740] ActiveTimeout:604 Mar 4 18:06:14 xxx vdr: [6740] Retry: Never ... Mar 4 18:31:14 xxx vdr: [6740] LastActivity: Never Mar 4 18:31:14 xxx vdr: [6740] ActiveTimeout: 2104 Mar 4 18:31:14 xxx vdr: [6740] Retry: Never ... goes on and on and no shutdown attempts... My current activity/timeout settings are: MinUserInactivity = 600 MinEventTimeout = 10 BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 12149 on Astra 19
Rob Davis wrote: I had to hack it to get it.. Don't remember how though.. Actually, CINE+ was split over several transponders CINE+ Promo;CSAT:12129:vC34:S19.2E:27500:168:112=fra,113=eng:0:0:8809:1:1086:0 CINE+ FOOT+;CSAT:12011:vC34:S19.2E:27500:170:120=fra:0:100:8809:1:1086:0 CINE+ FOOT+ 1;CSAT:12129:vC34:S19.2E:27500:161:84=fra,85=eng:0:100:8402:1:1086:0 CINE+ FOOT+ 2;CSAT:12129:vC34:S19.2E:27500:162:88=fra,89=eng:0:100:8403:1:1086:0 CINE+ FOOT+ 3;CSAT:12129:vC34:S19.2E:27500:163:92=fra,93=eng:0:100:8404:1:1086:0 CINE+ FOOT+ 4;CSAT:12129:vC34:S19.2E:27500:164:96=fra,97=eng:0:100:8405:1:1086:0 CINE+ FOOT+ 5;CSAT:12129:vC34:S19.2E:27500:165:100=fra,101=eng:47:100:8406:1:1086:0 CINE+ FOOT+ 6;CSAT:12129:vC34:S19.2E:27500:166:104=fra:0:100:8407:1:1086:0 CINE+ FOOT+ 7;CSAT:12129:vC34:S19.2E:27500:167:108=fra,109=eng:0:100:8408:1:1086:0 CINE+ FOOT+ 8;CSAT:12129:vC34:S19.2E:27500:168:112=fra,113=eng:0:100:8409:1:1086:0 CINE+ FOOT+ 9;CSAT:12129:vC34:S19.2E:27500:169:116=fra,117=eng:59:100:8410:1:1086:0 CINE+ FOOT+ 10;CSAT:12011:vC34:S19.2E:27500:170:120=fra,121=eng:0:100:8811:1:1090:0 CINE+ FOOT+ 11;CSAT:12129:vC34:S19.2E:27500:160:80=fra,81=eng:0:100:8413:1:1086:0 CINE+ FOOT+ 12;CSAT:12207:vC34:S19.2E:27500:170:120=fra,121=eng:62:100:8515:1:1086:0 CINE+ FOOT+ 13;CSAT:12129:vC34:S19.2E:27500:166:104=fra:0:100:8411:1:1086:0 CINE+ FOOT+ 14;CSAT:12129:vC34:S19.2E:27500:167:108=fra,109=eng:0:100:8412:1:1086:0 CINE+;CSAT:12011:vC34:S19.2E:27500:168:112=fra,113=eng:0:0:8810:1:1086:0 MAG CINE+ FOOT+;CSAT:12011:vC34:S19.2E:27500:0:224=fra:0:0:8812:1:1086:0 -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 12149 on Astra 19
Klaus Schmidinger wrote: Rob Davis wrote: Anyone know why VDR won't pick up the different channels on this frequency? All I get is Kiosque, but I know there are Cine+ Foot 1 2 3 4 etc..? apart from hacking it by hand, anyone know of a solution? There is no 12149 on Astra 19E. All there is is 12148H (which is apparently a German transponder) and 12129V, which I guess is what you meant. I also only have KIOSQUE;CSAT:12129:vC34:S19.2E:27500:0:0:0:0:8414:1:1086:0 in my channels.conf, and when I tune to that channel no other channels are added. Maybe they aren't broadcasting the necessary data? Or they broadcast it on a different transponder? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr CINE+ Promo;CSAT:12129:vC34:S19.2E:27500:168:112=fra,113=eng:0:0:8809:1:1086:0 CINE+ FOOT+ 1;CSAT:12129:vC34:S19.2E:27500:161:84=fra,85=eng:0:100:8402:1:1086:0 CINE+ FOOT+ 2;CSAT:12129:vC34:S19.2E:27500:162:88=fra,89=eng:0:100:8403:1:1086:0 CINE+ FOOT+ 3;CSAT:12129:vC34:S19.2E:27500:163:92=fra,93=eng:0:100:8404:1:1086:0 CINE+ FOOT+ 4;CSAT:12129:vC34:S19.2E:27500:164:96=fra,97=eng:0:100:8405:1:1086:0 CINE+ FOOT+ 5;CSAT:12129:vC34:S19.2E:27500:165:100=fra,101=eng:47:100:8406:1:1086:0 CINE+ FOOT+ 6;CSAT:12129:vC34:S19.2E:27500:166:104=fra:0:100:8407:1:1086:0 CINE+ FOOT+ 7;CSAT:12129:vC34:S19.2E:27500:167:108=fra,109=eng:0:100:8408:1:1086:0 CINE+ FOOT+ 8;CSAT:12129:vC34:S19.2E:27500:168:112=fra,113=eng:0:100:8409:1:1086:0 CINE+ FOOT+ 9;CSAT:12129:vC34:S19.2E:27500:169:116=fra,117=eng:59:100:8410:1:1086:0 CINE+ FOOT+ 11;CSAT:12129:vC34:S19.2E:27500:160:80=fra,81=eng:0:100:8413:1:1086:0 CINE+ FOOT+ 13;CSAT:12129:vC34:S19.2E:27500:166:104=fra:0:100:8411:1:1086:0 CINE+ FOOT+ 14;CSAT:12129:vC34:S19.2E:27500:167:108=fra,109=eng:0:100:8412:1:1086:0 I had to hack it to get it.. Don't remember how though.. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] FF card AV sync problems, possible fix to VDR (fwd)
Hi Werner, Were there problems? Morfsta On 2/23/07, Dr. Werner Fink <[EMAIL PROTECTED]> wrote: On Thu, Feb 22, 2007 at 06:18:11PM +, Morfsta wrote: > Hi Werner, > > Any idea when you will be able to release the new firmware for testing? I'm just testing the stuff in real live on my productions system ;) Knock on wood that this stays stable ... Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr ___ 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] vdr-1.5.1 & problems with the new shutdown code
Rolf Ahrenberg wrote:
No "assuming manual start of VDR" entry found on my logs, so this really
was on automatic wakeup for the timer.
If VDR did detect it as manual start, then something else must have
caused VDR to believe that there's an interactive user. Something
triggers the activity, maybe a plugin?
Mar 4 02:05:57 xxx vdr: [6748] next timer event at Sun Mar 4 10:58:00
2007
Mar 4 10:58:00 xxx vdr: [6688] timer 18 (5 1058-1130 'xxx') start
... and vdr just stays on ...
... and I assume that VDR started not more than 10 minutes before, eg.
after 10:48?
Please add the attached patch, it logs some more infos that might shed
light on this.
This gives log lines like this:
Mar 4 12:11:18 xx vdr: [3788] Manual Start check: Delta = 240
- means on VDR startup, the expected vs. now time was 240 seconds, VDR
started 4 minutes before planned.
The following log lines get dumped once a minute:
Mar 4 12:12:20 xx vdr: [3788] LastActivity: Never
Mar 4 12:12:20 xx vdr: [3788] ActiveTimeout: 62
Mar 4 12:12:20 xx vdr: [3788] Retry: Never
- No keyboard activity ever, no interactive user, ready to shut down
again since 62 seconds. Never tried to restart. Thats how it should look
like.
Mar 4 12:14:20 xx vdr: [3788] LastActivity:36
Mar 4 12:14:20 xx vdr: [3788] ActiveTimeout: -1164
Mar 4 12:14:20 xx vdr: [3788] Retry: Never
- This is after activity: Last key stroke 36 seconds ago, no automatic
shutdown for next 1164 seconds.
Cheers,
Udo
Index: vdr.c
===
--- vdr.c (Revision 874)
+++ vdr.c (Arbeitskopie)
@@ -1193,6 +1193,37 @@
// Main thread hooks of plugins:
PluginManager.MainThreadHook();
+
+
+#define DebugTimeouts
+#ifdef DebugTimeouts
+
+static time_t DebugTime = time(NULL);
+time_t Now = time(NULL);
+if (Now - DebugTime >= 60) {
+ time_t LastActivity = cRemote::LastActivity();
+ if (!LastActivity)
+ dsyslog("LastActivity: Never ");
+ else
+ dsyslog("LastActivity: %5i ",(int)(Now - LastActivity));
+
+ time_t ActiveTimeout = ShutdownHandler.GetUserInactiveTime();
+ if (!ActiveTimeout)
+ dsyslog("ActiveTimeout: Never ");
+ else
+ dsyslog("ActiveTimeout: %6i ",(int)(Now - ActiveTimeout));
+
+ time_t Retry = ShutdownHandler.GetRetry();
+ if (!Retry)
+ dsyslog("Retry: Never ");
+ else
+ dsyslog("Retry: %6i ",(int)(Now - Retry));
+
+ DebugTime = Now;
+ }
+
+#endif
+
}
if (ShutdownHandler.EmergencyExitRequested())
Index: shutdown.c
===
--- shutdown.c (Revision 874)
+++ shutdown.c (Arbeitskopie)
@@ -103,6 +103,8 @@
void cShutdownHandler::CheckManualStart(int ManualStart)
{
time_t Delta = Setup.NextWakeupTime ? Setup.NextWakeupTime - time(NULL) : 0;
+
+ dsyslog("Manual Start check: Delta = %i", (int)Delta);
if (!Setup.NextWakeupTime || abs(Delta) > ManualStart) {
// Apparently the user started VDR manually
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.1 & problems with the new shutdown code
On Sat, 3 Mar 2007, Udo Richter wrote: Check your log for the "assuming manual start of VDR" line around VDR startup. This indicates that the wakeup was more than 10 minutes away from the time that VDR remembered on last shutdown. No "assuming manual start of VDR" entry found on my logs, so this really was on automatic wakeup for the timer. Also check your setup.conf for the NextWakeupTime entry, thats where VDR remembers the planned wakeup time now. (This is a time_t, you can translate it with perl -e "print scalar localtime(1172945228)") Finally, there should be an "next timer event at" or "next plugin wakeup at" in the logs around shutdown that also indicates the time VDR planned to wake up. VDR # fgrep NextWakeupTime /etc/vdr/setup.conf NextWakeupTime = 1172998680 VDR # perl -e "print scalar localtime(1172998680)" Sun Mar 4 10:58:00 2007 VDR # fgrep "next timer" /var/log/vdr.log Mar 4 02:05:57 xxx vdr: [6748] next timer event at Sun Mar 4 10:58:00 2007 Mar 4 10:58:00 xxx vdr: [6688] timer 18 (5 1058-1130 'xxx') start Mar 4 11:30:00 xxx vdr: [6688] timer 18 (5 1058-1130 'xxx') stop Mar 4 11:30:09 xxx vdr: [6700] channel 4 (Nelonen) event Su 04.03.2007 11:30-12:30 'Alaston tiede' status 4 Mar 4 11:31:09 xxx vdr: [6688] deleting timer 18 (5 1058-1130 'xxx') ... and vdr just stays on ... BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.1 & problems with the new shutdown code
Jürgen Schilling wrote: I've the same problem with VDR 1.5.1... The VDR does not shutdown after a recording. It looks like VDR assumed the start to be manually, not automatically. Same for you: Check the logs for "assuming manual start of VDR", "next timer event at" and "next plugin wakeup at" messages, and check setup.conf for the NextWakeupTime line. These infos should explain what went wrong. Cheers, Udo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.1 & problems with the new shutdown code
Hi Rolf, I've the same problem with VDR 1.5.1... The VDR does not shutdown after a recording. I didn't find any entry in the logfile that the VDR will initiate a shutdown. With VDR 1.4.5 everything is working well and I use the same config files with VDR 1.5.1 and VDR 1.4.5. Even also the runvdr is identical. I use NVRAM-wakeup to wakeup the VDR. It works well if I do a manual shutdown on VDR 1.5.1, but not with the automatic shutdown... Regards, Juergen Rolf schrieb am Samstag, 3. März 2007 um 18:03: > Hi, > I've noticed some shutdown problems with vdr-1.5.1 in my setup: when my > vdr wakes up for a timed recording, it doesn't automatically shutdown > itself anymore after the recording is done. The MinEventTimeout is set > to 15 minutes and MinUserInactivity to 600 minutes, but in my case there > hasn't been any user activity, so vdr should have shutdown in 15 minutes > after the recording was stopped and the logs don't reveal anything > unusual. Have I misunderstood something? Does this automatic shutdown > feature still work in your setups? > BR, > -- > rofa > ___ > 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
