> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Matt Doran
> Sent: Thursday, August 09, 2007 8:59 PM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] How wakeup detects manual/auto poweron
>> Hi there,
>> The way this works is that when the myth shutdown code sets a
> wakeup time value in the database (can't remember which
> config setting).
>> Then when it starts up, if the current time is within 15
> minutes of the value in the DB it treats it as a "auto" startup.
>> Thanks,
> Matt
>> Michelle Dupuis wrote:
> > I agree...
> >
> > The problem I'm having is the script which puts the PC to
> sleep sets
> > the next wakeup time based on the next scheduled recording, OR the
> > next mythfilldatabase, whichever comes first. If the
> system wakes up
> > to mythfilldatabase, then the PC stays on indefinitely...
> >
> > Does anyone know if the wake time detection code
> (scheduled/manual) is
> > in a bash file (and if so which one)?
> >
> > MD
> >
> >
> >> -----Original Message-----
> >> From: mythtv-users-bounces at mythtv.org> >> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of John Veness
> >> Sent: Thursday, August 09, 2007 4:49 PM
> >> To: Discussion about mythtv
> >> Subject: Re: [mythtv-users] How wakeup detects manual/auto poweron
> >>
> >> Brian Steele wrote:
> >>
> >>> On 8/8/07, Michelle Dupuis <support at ocg.ca> wrote:
> >>>
> >>>> Can someone explain how on powerup, myth can detect
> whether it was
> >>>> started by ACPI wakeup, or by manual powerup?
> >>>>
> >>>> The manual powerup starts myth in the FE, while acpi
> wakeup starts
> >>>> myth in the Welcome screen.
> >>>>
> >>> I believe Myth looks at the upcoming recordings to decide
> >>>
> >> how it was
> >>
> >>> started. If you have the "stay on x minutes before
> >>>
> >> recording" setting
> >>
> >>> set to 20 minutes, then any upcoming recording scheduled
> within the
> >>> next 20 minutes will cause myth to think it was started
> >>>
> >> automatically.
> >>
> >>> If there are no upcoming recordings in that window, myth
> thinks it
> >>> was started manually.
> >>>
> >> I wonder if there could be a more elegant way of doing
> this, maybe by
> >> comparing the current time with the wakeup time stored in the BIOS?
> >>
> >> Cheers,
> >>
> >> John
> >>
> >> --
> >> John Veness, MythTV user, UK, DVB-T
> >> _______________________________________________
> >> mythtv-users mailing list
> >> mythtv-users at mythtv.org> >> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users> >>
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users> >
> >
> _______________________________________________
> mythtv-users mailing list
>mythtv-users at mythtv.org>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Ok - which script/code file is doing the check for within 15 minutes? I
need to modify that file to check for within 15 minutes of Mythfilldatabase
time too.
As for the other questions, I'm using a script called "acpi-wakeup" which
replaces "nvram-wakeup". It is command line compatible, uses the ACPI
interface to set BIOS wakeup time (no poking directly into NVRAM), and
checks for the next mythfilldatabase time.
MD