At line 1 changed 2 lines |
!Date Variables\\ |
|
!Date Variables |
[Server Variables] have additional variables that can be used in a CrushTask depending on the situation as well.\\ |
\\ |
At line 4 changed 22 lines |
{MM} month number\\ |
{MMM} month abbreviated\\ |
{MMMM} month full\\ |
{dd} day\\ |
{yy} or {yyyy} year\\ |
{HH} 24 hour\\ |
{mm} minute\\ |
{hh} 12 hour\\ |
{aa} AM or PM\\ |
{ss} seconds\\ |
{S} milliseconds\\ |
{EEE} weekday abbreviated\\ |
{EEEE} weekday full\\ |
{W} week number in the current month\\ |
{w} week number in the current year\\ |
{u} day number of the week\\ |
{D}or {DD} day number in the current year\\ |
{F} day of week in month\\ |
{z} general timezone\\ |
{Z} RFC 822 time zone\\ |
{J} julian date\\ |
{millis} millisecond time\\ |
{{{ |
{MM} month number |
{MMM} month abbreviated |
{MMMM} month full |
{dd} day |
{yy} or {yyyy} year |
{HH} 24 hour |
{mm} minute |
{hh} 12 hour |
{aa} AM or PM |
{ss} seconds |
{S} milliseconds |
{EEE} weekday abbreviated |
{EEEE} weekday full |
{W} week number in the current month |
{w} week number in the current year |
{u} day number of the week |
{D}or {DD} day number in the current year |
{F} day of week in month |
{z} general timezone |
{Z} RFC 822 time zone |
{J} julian date |
{millis} millisecond time |
At line 27 changed 2 lines |
{yesterday} millisecond time of yesterday (no variations)\\ |
{time} or {now} millisecond time of now (no variations)\\ |
{yesterday} millisecond time of yesterday (no variations) |
{tomorrow} millisecond time of tomorrow (no variations) |
{time} or {now} millisecond time of now (no variations) |
}}} |
At line 39 added 3 lines |
A trailing '!' indicates tomorrow. {MM!}{dd!}{yyyy!}\\ |
A trailing '!!' indicates next week. {MM!!}{dd!!}{yyyy!!}\\ |
A trailing '!!!' indicates next month. {MM!!!}{dd!!!}{yyyy!!!}\\ |
At line 44 added 2 lines |
A leading '-' indicates the modified date and time of the file {-MM}{-dd}{-yyyy} {-HH}{-mm}{-ss}{-S}\\ |
|
At line 49 added 2 lines |
''(future date/times such as tomorrow, next week, next month start with CrushFTP 10.0.0_32+)'' |
\\ |
At line 41 changed one line |
[Server Variables] have additional variables that can be used in a CrushTask depending on t he situation as well. |
CrushTask / Jobs can reference their schedule name with {scheduleName}\\ |
{task_error} is the most recent task's error.\\ |
{task_errors} are all the task errors accumulated so far.\\ |
{task_error_names} are the names of all the tasks that had errors so far.\\ |
{last_error} is the last task error encountered, if any.\\ |
{name} is the filename of the item and {stem} is the filename without extension and {ext} is just the extension.\\ |
{path} is the path including the filename of the item. {parent_path} is the path without the filename.\\ |
{real_path} is the actual OS notation for a file:// item using backslashes on windows, etc. and {real_parent_path} is the same without filename.\\ |
{url} is the URL referencing the item.\\ |
\\ |
---- |
Custom variables (defined with the UserVariable task)\\ |
\\ |
Variables starts with "GLOBAL_" are stored in jvm system properties it lives till the current jvm running.\\ |
Variables starts with "PERSIST_" are stored in xml file at CrushFTP install folder it will be stored until the xml file is there.\\ |
\\ |
---- |
{thread_dump} - Create thread dump list to debug the server.\\ |
---- |
Misc |
\\ |
{item_count} and {items_count} gives the size of the list in terms of number of items\\ |
---- |