This bug report is several years old. I looked at both the Linux man page for at(1) and at the SUSv3 man page, and neither allow the date to be specified before the time in the "timespec" (SUSv3 terminology).
Furthermore, the default output of Linux at(1) doesn't match SUSv3, but if you set POSIXLY_CORRECT, it does. However, even the output specified in SUSv3 is not valid as an input timespec, per SUSv3 or Linux at(1). Is this really a bug, or just a poor design choice? In the latter case, can this report be closed? -Jonathan Hankins -- -------------------------------------------------------------------------- Jonathan Hankins Homewood City Schools [EMAIL PROTECTED] -------------------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
