[vdr] "next timer event" problem

[Usenet-372114@zocki.toppoint.de (Rainer Zocholl)]

Hello

Up till now VDR ran beautiful!
(I gave one Hauppage DVB-s 2.1 to repair which blocks the PC(MS-6215)
often after a longer poweroff), and gave back the nova...)
(If it would warn about a full disc watching would be less stressy ;-)
But that's not the problem. The disc is free enough.)


But yesterday the timer failed:
Is there problem with "single date"?

I scheduled using "1 Schedule" : Record today, the 29th, 
starting 21:54, 
but VDR did not record!

Worse:
Despite of the next weekly event at 0:59 it always says
the next event is at the 29th, now meaning next month
and nvram-wakup disables wake up entirely.

If i look into "2 timers" i see the record of the 29th on the
top position, but there are a lot other "repeted" recordings before
the 29. will be on schedulke again.


3 Questions:
Why did the record programmend on the 29 (at approx 21:50, i'm QUITE
sure that it was before the actual start time)  for the 29 21:54 did 
not start?
Why is the "next" this 29th but with a false time?
Why is it listed on the top timer position if the programming 
was interpreted as: "Next month"?



Fourth(not directly a VDR problem) nvam-wakup disables 
the wakup function entirely.


May it depend on February (too), which do not have a 29th this year?









timer.conf:
...
1:2:MTWTF--:1133:1201:50:6:
1:11:MTWTFS-:0059:0201:50:3:
1:5:MTWTFSS:1929:2000:50:3:
...
1:13:29:2154:2211:50:7:singel



Jan 29 23:54:00 msi vdr[672]: confirmed
Jan 29 23:54:00 msi vdr[672]: executing '/video/pwroff 0 -1012344539 13 'singel' 0'
Jan 29 23:54:01 msi pwroff: no one logged in

Jan 29 23:54:01 msi pwroff:
Jan 29 23:54:01 msi pwroff: WakeUp  : Enabled (0x4D)
Jan 29 23:54:01 msi pwroff: Date    : 29 (0x1D)
Jan 29 23:54:01 msi pwroff: Hour    : 19 (0x13)
Jan 29 23:54:01 msi pwroff: Minute  : 24 (0x18)
Jan 29 23:54:01 msi pwroff: Second  : 00 (0x00)
Jan 29 23:54:01 msi pwroff: Checksum: 0xA5C9
Jan 29 23:54:01 msi pwroff:
Jan 29 23:54:01 msi pwroff:
Jan 29 23:54:01 msi pwroff: WakeUp  : Disabled (0x45)
Why???? (That might be caused by the "wrong" event )
Jan 29 23:54:01 msi pwroff: Date    : 29 (0x1D)
Jan 29 23:54:01 msi pwroff: Hour    : 19 (0x13)
Jan 29 23:54:01 msi pwroff: Minute  : 24 (0x18)
Jan 29 23:54:01 msi pwroff: Second  : 00 (0x00)
Jan 29 23:54:01 msi pwroff: Checksum: 0xA5C1
Jan 29 23:54:01 msi pwroff:

Jan 30 01:51:19 msi vdr[668]: executing '/video/pwroff 0 -1012351577 13 'single' 0'
Jan 30 01:51:22 msi pwroff: no one logged in
Jan 30 01:51:23 msi pwroff:
Jan 30 01:51:23 msi pwroff: WakeUp  : Disabled (0x45)
Jan 30 01:51:23 msi pwroff: Date    : 29 (0x1D)
Jan 30 01:51:23 msi pwroff: Hour    : 19 (0x13)
Jan 30 01:51:23 msi pwroff: Minute  : 24 (0x18)
Jan 30 01:51:23 msi pwroff: Second  : 00 (0x00)
Jan 30 01:51:23 msi pwroff: Checksum: 0xA5C1
Jan 30 01:51:23 msi pwroff:
Jan 30 01:51:23 msi pwroff:
Jan 30 01:51:23 msi pwroff: WakeUp  : Disabled (0x45)
Jan 30 01:51:23 msi pwroff: Date    : 29 (0x1D)
Jan 30 01:51:23 msi pwroff: Hour    : 19 (0x13)
Jan 30 01:51:23 msi pwroff: Minute  : 24 (0x18)
Jan 30 01:51:23 msi pwroff: Second  : 00 (0x00)
Jan 30 01:51:23 msi pwroff: Checksum: 0xA5C1
Jan 30 01:51:23 msi pwroff:

Wakeup Disabled? Why? 




#!/bin/sh
# setRTCwakeup $(($1 - 300))
LOGGER='logger -t pwroff'

$LOGGER VDR shutdown 1:$1 2:$2 3:$3 4:$4 5:$5 A:$*
sync

touch /tmp/sdsdfsd ; rm /tmp/sdsdfsd
w | grep " 0 user" > /tmp/sdsdfsd
if [ -s  /tmp/sdsdfsd ]
then
  $LOGGER no one logged in
else
  w | grep user | $LOGGER
  exit 1
fi



sync


/bin/ps auxwww | /bin/grep "pwroff" | /bin/grep -v vdr| /usr/bin/wall
/bin/echo "Shutdown from VDR  1:$1 2:$2" | /usr/bin/wall


# test:nvram-wakeup -s $((`date +%s`+ 10 * 60))
/sbin/nvram-wakeup | $LOGGER
if /sbin/nvram-wakeup -s $1 ; then
     /sbin/nvram-wakeup | $LOGGER

     sleep 3s
     /bin/echo "Shutdown from VDR NOW" | /usr/bin/wall
     logger -t "$0" VDR shutdown delay  1:$1 2:$2 3:$3 4:$4 5:$5 A:$*

     echo $1 > /nvramboot

     sync
     sync
     shutdown -r now
fi

Rainer---<=====>                         Vertraulich
             //  
           //                              
         <=====>--------------ocholl, Kiel, Germany ------------