cron, atd, anacron, other wtf

[John Richard Moser]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What's with all the crap that starts up at boot?  It's a waste of time,
install space, and memory to start a lot of useless things; boot time is
affected when scripts that take 2-3 seconds to load on a SATA-150 Athlon
64 system are uselessly piled on top of one another.

Here's a list of useless things I've noticed in rc3.d and rc5.d:

 S20rsync:  rsyncd -- rsync can work over ssh without an rsyncd; we
            hardly need that running or attempting to run unless
            specifically configured.  It doesn't even start by default
            anyway, the script just pokes at defaults and decides you
            don't want to start it.
 S89cron
 S89anacron
 S89atd:    Periodic Command schedulers -- THREE?  Please pick one to
            use and stick with it.  If we need to use others, we'll turn
            them on, we obviously know what we're doing if we know we
            need any of these

The question of sysklogd and klogd comes to mind as well-- are these
different, do we need 2?
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

    Creative brains are a valuable, limited resource. They shouldn't be
    wasted on re-inventing the wheel when there are so many fascinating
    new problems waiting out there.
                                                 -- Eric Steven Raymond
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDxI8ZhDd4aOud5P8RApV/AJ99vqdkju5NhfqdSl7ecTRQsNCGawCeLSZi
2BWMYFlmqqMJPRMVms0zcG4=
=/Qa2
-----END PGP SIGNATURE-----