[mythtv-users] mythshutdown

[jksjdevelop]

FWIW mythshutdown stopped working for me when I upgraded to kernel 4.15 
ubuntu 18.04 from 16.04. The machine would shutdown but fail to reboot.

I had to replace

echo 0 > /sys/class/rtc/rtc0/wakealarm      #this clears your alarm.
echo $1 > /sys/class/rtc/rtc0/wakealarm     #this writes your alarm

with
sudo rtcwake -v -m no -t $1

in setwakeup.sh

refhttps://www.mythtv.org/wiki/ACPI_Wakeup

Alyhough the BIOS clock is definitely UTC I was previously adding the 
UTC offset, this is no longer necessary with mythshutdown providing the 
correct no of seconds until the next recording.

N.B. rtcwake has to be added to the sudoers list.

On 24/05/18 10:07, Jeff wrote:
> Hallo all,
>
> I have the feeling that mythshutdown is reversing the timezone offset
> when writing the wake-up time. e.g.:
>
> $ mythshutdown --setscheduledwakeup
> Setting scheduled wakeup time: Attempting to connect to master server...
> Wakeup time given is: 24.05., 11:20 (local time)
> $ cat /proc/driver/rtc
> rtc_time	: 08:50:16
> rtc_date	: 2018-05-24
> alrm_time	: 13:20:00
> alrm_date	: 2018-05-24
> [ ... ]
>
> At the moment, I am in UTC+2. The above rtc time is correctly UTC, but
> the alrm_time seems to be UTC+4.
>
> Where is my mistake?
>
> Regards
>
> Jeff
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20180525/a3b4a091/attachment.html>