%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµùÕ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream
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.