-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 16 September 2003 06:2018pm, Ben Pitzer wrote: > apt (in either Debian or any RPM distro) is not a thing that should > probably be put in a cron job. All too often it requires some level > of user interaction to configure packages, or in Debian's case, can > leave some packages un-updated because of new file dependencies that > are missing.
Sure. This is why you get an email telling you what has been going on. It's always a compromise. How much time can you afford to spend per server? Can you afford to automate and then review the results, to see if there's any interaction needed? Besides, with a set up like this you are: a) getting bugtraq notifications (you are subscribed to bugtraq, right?) b) getting RH emails with security alerts c) receiving your update server's notifications on what's new d) getting an email from each server in the server farm So you should be ontop of things and know if and when your intervention is required. This is not perfect, but it's a possible choice. Mr. DRM has just more than one home machine that needs attention. So it's his call. Salut, Sinner - -- http://www.ibiblio.org/sinner/ Linux User # 89976 Testing Mandrake 9.1 - Linux Machine # 38068 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/Z7YLSGQa4/zQ9e8RAhBFAKCXQD1ajD2gZ0i+Z+Nt/PInPzD6awCfRQTK 8zNNaXTwu2S2lK1CgbEnVlg= =PG/1 -----END PGP SIGNATURE----- -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
