Bug #14722
closed
Snort Rule Update time settings does not create cron job correctly with certain times
0%
Description
What happens is that when a combination of update interval and hour is set that adds up to 24, the script that creates the cron job incorrectly inputs 24 into the parameters, which is invalid.
For example, inputting the settings in the GUI to update every 12 hours, and start at 12:10, puts the following into crontab:
10 12,24 * * *
This is invalid, as 24 should be 0 instead; there is no 24th hour.
It should be:
10 0,12 * * *
Of course when this happens, it fails silently with no logging, as the job doesn't even attempt to run.
It does appear to be fine if the values add up to over 24. I tried setting it to update every 12 hours, starting at 13:10, and it properly puts in the following:
10 13,1 * * *
This has been tested in PFSense Plus 23.05.1 with Snort version 4.1.6_7
Files
| 12 10 update time.png (61.1 KB) 12 10 update time.png | GUI showing 12 hour update interval selected with 12:10 start time | ||
| 13 10 update time.png (61.1 KB) 13 10 update time.png | GUI showing 12 hour update interval selected with 13:10 start time | ||
| 13 1 crontab.png (39.4 KB) 13 1 crontab.png | crontab results of 12 hour update interval with 13:10 start time | ||
| 12 24 crontab.png (39.2 KB) 12 24 crontab.png | crontab results of 12 hour update interval with 12:10 start time |
Updated by Bill Meeks over 1 year ago
This is a duplicate of bug 14723. My report of the user-identified issue and the acutal user's report of the same issue passed each other in the ether.
This issue can be marked "Resolved" when Pull Request 1288 (https://github.com/pfsense/FreeBSD-ports/pull/1288) is merged.
Updated by 
