vixie-cron will be started before services like xinetd(50), ntpd(56),
sendmail(80) or postgresql(85). There are race conditions possible
(e.g. an entry '@reboot vacuum_postgres_dbs') causing a bad behavior.
I think vixie-cron should be started at position 90 or higher.
The same is true for at-3.1.8-4 also.
Still in Pinstripe.
Still in RC1 (see #15335 also)
It's fixed in vixie-cron-3.0.1-55.