Introductionat.exe is a commandline scheduler on Win32, similar in concept to *nix cron and at. It's run from a cmd.exe window, and allows you to add, remove, and view scheduled commands. Other tools exist for MS-Windows scheduling, but are outside the scope of this document.
(at time /date command)
at 2:00 /every:Th C:\Perl\bin\perl.exe C:\perls\foo.pl --options --and --arguments
at 14:00 /next:T C:\Perl\bin\perl.exe C:\perls\foo.pl --options --and --arguments
- at.exe evidently runs in an environment with no path to perl.exe. Therefore the script must be called in this form: drive:\path\to\perl drive:\path\to\script.pl
- cmd.exe commands apparantly cannot exceed 256 characters. See Win32::AdminMisc below to get around this.
- at.exe is included only in true 32bit versions of MS-Windows (NT, 2k, XP), and isn't part of 16bit versions of MS-Windows (3.(0|1)|9(5|8)|me). If one of the latter group is your development platform, you have my deepest condolances. %^P
- Mistakes in this doc are quite possible - corrections, additions, and rotton kiwifruit welcome. Well, maybe not the rotton fruit.
- Win32::AdminMisc - ScheduleAdd()
- Win32::AdminMisc - ScheduleDel()
- Win32::AdminMisc - ScheduleGet()
- Win32::AdminMisc - ScheduleList()
- AT Tasks Cannot Be Viewed Using the Task Scheduler Tool
- HOW TO: Modify a Scheduled Task to Repeat By Minutes or Hours
- Task Scheduler Service on Windows NT
- A Task That Is Scheduled with the AT Command May Stop After 72 Hours
- HOW TO: Use the AT Command to Schedule Tasks
- at /?
Thanks to a monk or three (you know who you are) for pre-post critique, who shall remain nameless lest the sins of this post be visited upon them verily unto three generations
Update: thanks to to replying monks for pointing out what appears to be substantial problems with win32 at. I've not encountered problems myself, but have no reason to doubt that they exist. Please, read the rest of this thread for yourself *before* using my examples in any situation that's at all important. Caveat Usor