Hi, my scenario was: > echo "shutdown -h now" | at now +240minutes
It is executed from /etc/rc.local at system startup. The difference I see that I used a Raspberry Pi. Maybe an ARM only issue? (Have no access to the affected Raspi for the next 4 days, so I cannot test more atm, sorry) Regards, Markus. Am 13. Februar 2019 10:24:31 MEZ schrieb Karl Stenerud <[email protected]>: >Hi, > >I tried reproducing the error, but it didn't trigger for me: > >root@tester:~# date >Wed Feb 13 09:21:00 UTC 2019 >root@tester:~# at now +900minutes >warning: commands will be executed using /bin/sh >at> ls >at> <EOT> >job 3 at Thu Feb 14 00:21:00 2019 >root@tester:~# atq >3 Thu Feb 14 00:21:00 2019 a root >root@tester:~# uname -a >Linux tester 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC >2019 x86_64 x86_64 x86_64 GNU/Linux >root@tester:~# lsb_release -rd >Description: Ubuntu 18.04.2 LTS >Release: 18.04 >root@tester:~# at -V >at version 3.1.19 > > >Could you put together a test case that will trigger every time? > > >** Changed in: at (Ubuntu) > Status: New => Incomplete > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1815672 > >Title: > "at now +240minutes" calcultes wrongly if passing through midnight > >Status in at package in Ubuntu: > Incomplete > >Bug description: > > at --version > at version 3.1.19 > > uname -a >Linux pi3 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l >armv7l armv7l GNU/Linux > > lsb_release -rd > Description: Ubuntu 18.04.2 LTS > Release: 18.04 > > Error description: >Let´s assume it is February, 12th, 10 pm and you want "at" to execute a >command 4 hours from now, so at February 13th, 2 am in the morning. >If running "at now +240minutes" now, this will result in the following >"atq": > 19 Tue Feb 12 02:00:00 2019 a root > > So it is "Feb 12" instead of "Feb 13". > >Even worse, if you add another command to the "at queue" now without >emptying it first, the original command in the queue will be executed >directly, because obviously at notices now that there is some command >to be executed from the past. >This can be annoying when e.g. shutting down a remote server 4 hours >after it has been powered up with "at". > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/at/+bug/1815672/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815672 Title: "at now +240minutes" calcultes wrongly if passing through midnight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1815672/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
