Hi! I use epgsearch's searchtimer to record my favorite series. But there could be a problem when using automatic shutdown and wakeup. When there is no event in the current epg, the searchtimer will not be updated any more. The shutdown script will get no wakeup time, because there is no timer. The VDR will do no wakeup, and no more searchtimer records will be done. Maybe an option could be added to VDR to force a boot once a day. When the next timer is later than a specific time, set the wakeup time to this time. So you could make sure, that VDR is booted once a day, and the searchtimer could be updated. No searchtimer recording would be lost.
Thomas
Am 14.09.2014 um 12:02 schrieb Thomas Maaß:
Hi! I use epgsearch's searchtimer to record my favorite series. But there could be a problem when using automatic shutdown and wakeup. When there is no event in the current epg, the searchtimer will not be updated any more. The shutdown script will get no wakeup time, because there is no timer. The VDR will do no wakeup, and no more searchtimer records will be done. Maybe an option could be added to VDR to force a boot once a day. When the next timer is later than a specific time, set the wakeup time to this time. So you could make sure, that VDR is booted once a day, and the searchtimer could be updated. No searchtimer recording would be lost.
It is not the job of the vdr to do such OS depending actions. Use the ACPI Wakeup addon for this task like most vdr distributions do.
Gerald
!DSPAM:54156be3490091730197352!
Am Sun, 14 Sep 2014 12:02:09 +0200 schrieb Thomas Maaß mase@setho.org:
|Hi! |I use epgsearch's searchtimer to record my favorite series. |But there could be a problem when using automatic shutdown |and wakeup. When there is no event in the current epg, the |searchtimer will not be updated any more. The shutdown script |will get no wakeup time, because there is no timer. The VDR will |do no wakeup, and no more searchtimer records will be done. |Maybe an option could be added to VDR to force a boot once a |day. When the next timer is later than a specific time, set the |wakeup time to this time. So you could make sure, that VDR is |booted once a day, and the searchtimer could be updated. No |searchtimer recording would be lost. | |Thomas |
Hi,
for this special epgsearch szenario, i have written a very minimalistic autotimer plugin. If you are interested I can post it.
Alex
Why don't you just use a cron job for this?
On Sun, Sep 14, 2014 at 3:02 AM, Thomas Maaß mase@setho.org wrote:
Hi! I use epgsearch's searchtimer to record my favorite series. But there could be a problem when using automatic shutdown and wakeup. When there is no event in the current epg, the searchtimer will not be updated any more. The shutdown script will get no wakeup time, because there is no timer. The VDR will do no wakeup, and no more searchtimer records will be done. Maybe an option could be added to VDR to force a boot once a day. When the next timer is later than a specific time, set the wakeup time to this time. So you could make sure, that VDR is booted once a day, and the searchtimer could be updated. No searchtimer recording would be lost.
Thomas
-- gpg-id: ccdbc2cf https://www.setho.org/people
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Why don't you just use a cron job for this?
Why to use cron if the ACPI wakeup addon has a setting for this?
Because you don't need to bother with a whole plugin just for that. But, if the end result is the same then who cares how you got there I guess. My preference is to not make things more difficult or dependent than they need to be so for me I wouldn't bother with a plugin when my system already supports what I'm looking for.
Am 14.09.2014 um 19:42 schrieb VDR User:
Why don't you just use a cron job for this?
Why to use cron if the ACPI wakeup addon has a setting for this?
Because you don't need to bother with a whole plugin just for that.
It is an addon, no plugin, just some scripts and there is a big chance that it is already installed. How else would his computer start to record scheduled events?
Gerald
!DSPAM:5415d62873265520375805!
Why don't you just use a cron job for this?
Why to use cron if the ACPI wakeup addon has a setting for this?
Because you don't need to bother with a whole plugin just for that.
It is an addon, no plugin, just some scripts and there is a big chance that it is already installed. How else would his computer start to record scheduled events?
I misunderstood, I thought it was some plugin. Regardless though it doesn't take anything special to do what he wants. In addition to a single line cron, Udo posted what sounds like a good alternative as well. No extra scripts/packages/whatever necessary.
As far as how he manages `sleeping` and `waking` his system, there's more than one way to do that so who knows?
Why don't you add a 5 minute every day timer with a low priority and automatic deletion? That should pretty much do the trick. jm2c.
On 14. September 2014 12:02:09 MESZ, "Thomas Maaß" mase@setho.org wrote:
Hi! I use epgsearch's searchtimer to record my favorite series. But there could be a problem when using automatic shutdown and wakeup. When there is no event in the current epg, the searchtimer will not be updated any more. The shutdown script will get no wakeup time, because there is no timer. The VDR will do no wakeup, and no more searchtimer records will be done. Maybe an option could be added to VDR to force a boot once a day. When the next timer is later than a specific time, set the wakeup time to this time. So you could make sure, that VDR is booted once a day, and the searchtimer could be updated. No searchtimer recording would be lost.
Thomas
-- gpg-id: ccdbc2cf https://www.setho.org/people
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Am 14.09.2014 12:02, schrieb Thomas Maaß:
Maybe an option could be added to VDR to force a boot once a day. When the next timer is later than a specific time, set the wakeup time to this time.
You could hack this into the shutdown script itself.
Tomorrow=$(($(date +%s)+86400))
would be the time in exactly 24 hours, and in the same epoch format as the $1 parameter of the shutdown script. So if $1 equals 0, or $Tomorrow is less than $1, use $Tomorrow instead.
For completeness, you can also tell VDR that this is the actual expected boot time, by modifying setup.conf *after* VDR terminated:
sed -i -e "s/^NextWakeupTime = .*/NextWakeupTime = $Tomorrow/" setup.conf
That way, VDR will wake up with no timer nearby, and as it just don't know what went wrong, it'll shut down again 6 minutes later.
Cheers,
Udo