You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The render API states ABSOLUTE_TIME is in the format HH:MM_YYMMDD, YYYYMMDD, MM/DD/YY, or any other at(1)-compatible time format., and yet the examples just below that don't follow at behaviour at all.
Example: &from=january+1 (shows data since the beginning of the current year)
$ echo 'ls' | at january 1
job 1 at Sun Jan 1 12:34:00 2017
Not only does it use the current time of day, it uses january 1 of next year, not the current year.
Or possibly my favourite; this works in graphite: &from=janthisisntreallyamonth+1
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
What is the state of at(1) support?
The render API states
ABSOLUTE_TIME is in the format HH:MM_YYMMDD, YYYYMMDD, MM/DD/YY, or any other at(1)-compatible time format.
, and yet the examples just below that don't follow at behaviour at all.Example:
&from=january+1 (shows data since the beginning of the current year)
$ echo 'ls' | at january 1
job 1 at Sun Jan 1 12:34:00 2017
Not only does it use the current time of day, it uses january 1 of next year, not the current year.
Or possibly my favourite; this works in graphite:
&from=janthisisntreallyamonth+1
The text was updated successfully, but these errors were encountered: