Crontab Syntax
The following screenshot shows how to configure time-driven Input Agents with crontab syntax. New entries can be created via the context menu.
The syntax used in Lobster_data is similar to the crontab syntax in UNIX systems. However, the numbering of weekdays differs from the UNIX syntax. It starts with 1 for Sunday.
In column Day, for example, a 1 stands for the first day of the month, an L stands for the last day of a month, and a * means every day.
Important note: In any case, avoid a single asterisk (*) in the Seconds column, because that means every second and would have a very strong impact on performance.
Important note: If a job still runs when a new start time is reached, the new start time is ignored.
The following table shows some examples of setting the time points using crontab syntax. For comprehensive explanations and examples on the topic of crontab syntax, please refer to external sources. This is a commonly used concept.
|
Seconds |
Minutes |
Hour |
Day |
Month |
Weekday |
Meaning |
|
0 |
0 |
* |
* |
* |
* |
Every hour. |
|
0 |
15 |
10 |
* |
* |
1 |
Every Sunday at 10:15. |
|
0 |
*/20 |
* |
* |
* |
* |
Every 20 minutes, starting from full hours and on the full hour. Example: Let's assume you save your profile at 16:56 with these settings. Then it runs at 17:00, 17:20, 17:40, 18:00, 18:20, ... |
|
0 |
*/21 |
* |
* |
* |
* |
Every 21 minutes, starting from full hours and on the full hour. Example : Let's assume you save your profile at 16:56 with these settings. Then it runs at 17:00, 17:21, 17:42, 18:00, 18:21, ... Note: If you really want the next profile run 21 minutes after the last run, please use intervals. |
|
*/10 |
* |
* |
1 |
12 |
* |
Every 10 seconds on the 1st of December (starting from full minutes and to the full minute). |
|
0 |
*/10 |
6-8,16-19 |
* |
* |
* |
Every 10 minutes between 6-8 and 16-19 hours (starting from full hours and on the full hour). |