New Year Bug in At Command

Written in 2010, 15 years ago. Technology moves fast, so some details may be out of date.

TL;DR: On Debian Lenny and Ubuntu, running 'at tomorrow' on 31 December 2010 scheduled the job for January 2012, a full year late. Check the date it reports.

If you're writing an "at" job today, to run at the beginning of the New Year, make sure you check when "at" states the job is going to run. On my up to date Debian Stable (Lenny) system running "at" version 3.1.9, "tomorrow" is a year out. Same problem exists on my up to date Ubuntu box running "at" version 3.1.11:

mike@alfa:~$ date
Fri Dec 31 12:48:04 GMT **2010**

mike@alfa:~$ echo|at today
warning: commands will be executed using /bin/sh
job 5 at Fri Dec 31 12:48:00 **2010**

mike@alfa:~$ echo|at tomorrow
warning: commands will be executed using /bin/sh
job 6 at Sun Jan  1 12:48:00 **2012**

I wonder if this happens every year?