-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/12/11 10:38, Sthu Deus wrote: > Thank You for Your time and extended answer, Joe: > >> The general rule of thumb is to automatically update only workstations >> and test servers, never production servers. >> >> There is no way that automation can know whether it is wise to apply a >> particular update immediately, to wait a while, or not do it at all in >> cases of serious error. While errors (in Stable, at least) are >> extremely rare, the cost to a production server could be enormous. > > So, in case of workstations, we have no options besides these two: > either risk or manual update - these are the options?
have a look at $ apt-cache search cron-apt cron-apt - automatic update of packages using apt-get it's working nicely in quite big environments - -- |_|0|_| | |_|_|0| "Heghlu'Meh QaQ jajVam" | |0|0|0| -------- kuLa --------- | gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO5zl2AAoJEOqHloDBALTKxs8H/AltUZ7+lfg6PKFqDjukAGcn p69QG5qrYZDbVl29Aj79czCF/sltqjSNByJ9EksWjo63TS5N1Qri84tG1sO9RuqH cbxE4KgrN4+SlFtwaRkQLvwHwrSddPA4armtTAuWMHoO0Zgz1OErCxo9IGSLKNk8 0r752P0+rWlw2iaRu/f/iKdbiROK9JNGfZ1n5HHIGvLSbGNSMZOI1qIvs1weCgLt ygb+PCSZQhn5Zh93STGJ6oMhQsgfBxxM/6FFWKE6iczn/WRjkuOnX1XFHBYhjPaj Qd4QLDhkTdKks1FQzGCD5xWtLFcwKvJspAJ6UIPSnTWOFN5y7HAtEmWQh8SJeHY= =j3gs -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee73976.4020...@kulisz.net
