Dear Maintainer, When setting the time to 19 Jan 2038 3:14 GMT using "date 011903142038" the crond gets high load. Inspection of the cronie code, the meanloop of cron is controlled by a time value that becomes buggie after 0x7fffffff (19/01/2038) Probably cron_sleep is wrong. The actual sleep() is never called after 2038 The time is used to calculate the delay value but when used as unsigned the value becomes negative. it will continously run in the loop causing a high load of the cron daemon.
Thank you for reporting this bug! cron_sleep was recently updated to address a different issue, but it may apply to your bug. Would you try testing cronie with the changes in this commit [1] applied? Also, this bug has been forwarded upstream if you would like to contact the upstream maintainer directly about this issue. [1] https://github.com/cronie-crond/cronie/commit/78e634967d6886339be57854f0e11c6ab1fb73cd Thank you,
I have not been able to reproduce this bug. It is already forwarded upstream for further discussion.
Control: tags 1053873 = wontfix This is the year 2038 problem for 32-bit architectures. Debian has release goals for fixing or working around this issue for most 32-bit architectures, but based on Debian's wiki, i386 will not be transitioning time_t for 64-bit time [1]. [1] https://wiki.debian.org/ReleaseGoals/64bit-time Best,