-----BEGIN PGP SIGNED MESSAGE-----
On 28 Jul 1997, Eloy A. Paris wrote:
> just for curiosity: in Debian versions prior to 1.3 there was not
> at daemon (atd). After I upgraded to 1.3 there is an atd process
> hanging around. Does anyone know why? I guess at processing was done
> by crond in previous version, why did it change?
Before, cron was set to call atrun every 1 or 5 minutes, forcing disk
reads and basically making any power-management functions useless without
disabling at. Now atd can cache its state, and doesn't need to read the
drive (changing an atime stamp) every minute, so disks can cycle down. If
you aren't running any at tasks, atd will get itself swapped out and stay
there in any memory crunch.
- --
| Live never to be ashamed if anything
Scott K. Ellis | you do or say is published around the world --
[EMAIL PROTECTED] | even if what is published is not true.
| -- Illusions
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
iQCVAwUBM91BPqCk2fENdzpVAQGkowQAplMyVdvhaRKIgENVOKlZo4UfPLkIAB83
Y8EEKoXTiCObCbbHw9CucJI0C3mhH+8L3l6c11Zd9XHI5L9hvfPcwpgNEnd6Dn3k
6Dvsq3+ri3s0o+yuEFLpfmREnY0mDDrGBRZPnDM/De+mg8W6oKmI6u5QotXJ3A4b
KVb89H5I97o=
=NR9m
-----END PGP SIGNATURE-----
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
