Your message dated Mon, 28 Dec 2020 00:25:30 +0100 with message-id <[email protected]> and subject line Re: Bug#539347: util-linux: rtcwake reads rtc time 1 hour ahead (delta=-3600) has caused the Debian Bug report #539347, regarding util-linux: rtcwake's conversion from local time (EDT) to UTC is off by 8 hours. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 539347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539347 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: util-linux Version: 2.25.2-6 Severity: normal Dear Maintainer, rtcwake's conversion from local time to UTC is broken. My system is set to the EDT timezone, which is -4 hours from UTC. However, rtcwake adds 8 hours to my local time when converting to UTC. This results in the wake timer being off by 8 hours. For example, to have rtcwake suspend to RAM and then wake at 11:04 PM EDT the same day, I need to use the following command: rtcwake -m -l -t $(date +%s -d "tomorrow 07:04") The expected behavior would be to enter the time in EDT as I used the -l flag to indicate the use of local time. I would expect the following command to achieve the same behavior: rtcwake -m -l -t $(date +%s -d "today 23:04") *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I attmepted to use rtcwake to suspend my system to RAM and wake the system at a specified local time. * What exactly did you do (or not do) that was effective (or ineffective)? Through testing, I discovered I needed to adjust local time +8 hours to achieve the expected behvaior. * What was the outcome of this action? rtcwake now wakes the system as expected. * What outcome did you expect instead? I expected to be able to enter the time using my correct local time (EDT). -- System Information: Debian Release: 8.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages util-linux depends on: ii initscripts 2.88dsf-59 ii libblkid1 2.25.2-6 ii libc6 2.19-18+deb8u7 ii libmount1 2.25.2-6 ii libncurses5 5.9+20140913-1+b1 ii libpam0g 1.1.8-3.1+deb8u2 ii libselinux1 2.3-2 ii libslang2 2.3.0-2 ii libsmartcols1 2.25.2-6 ii libtinfo5 5.9+20140913-1+b1 ii libuuid1 2.25.2-6 ii lsb-base 4.1+Debian13+nmu1 ii tzdata 2016j-0+deb8u1 ii zlib1g 1:1.2.8.dfsg-2+b1 util-linux recommends no packages. Versions of packages util-linux suggests: ii dosfstools 3.0.27-1 ii kbd 1.15.5-2 ii util-linux-locales 2.25.2-6 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 2.17 * Kevin Mitchell <[email protected]>: > In spite of the fact that I get the correct restult from > $date > Tue Jul 28 23:55:01 EDT 2009 > $sudo hwclock > Tue 28 Jul 2009 23:54:48 EDT -0.969058 seconds > > I get > > $ sudo rtcwake -v -a -s 10 -m standby > Using local time. > delta = -3600 > tzone = 18000 > tzname = EDT > systime = 1248839626, (UTC) Wed Jul 29 03:53:46 2009 > rtctime = 1248843226, (UTC) Wed Jul 29 04:53:46 2009 > alarm 0, sys_time 1248839626, rtc_time 1248843226, seconds 10 > rtcwake: wakeup from "standby" using /dev/rtc0 at Wed Jul 29 00:53:57 2009 It appears upstream fixed this in commit 1da17ec6c1a22ae15fd4bf219d693e612b4bfe58. Best, Chris
--- End Message ---
