This report is related to #13353.
There doesn't exists any reason to start anacron before all other services
(network, mail, nfs, yp) which a started job can requiring.
Imagine a job like `id nis-user || do_bad_things'! Sometimes
`do_bad_things' will be executed, sometimes not.
Fixed in 2.3-9
Although it will be started at pos 95 now, it will be shutdowned at pos 92
still. I think this values should be symmetrically, so I am recommending the
pair `95 05'.
Doesn't matter since anacron is not a daemon. (chkconfig just doesn't have a way
to have a process starting when entering a runlevel without terminating it when