automate updates in Lenny
in [Debian]
|
Prev: How do I get the mbr package to do its job quietly?
Next: Keyboard gets stuck when closing PPP (was: Problems when logging out Gnome)
From: Jozsi Vadkan on 7 Apr 2010 15:00 how do you automate the updates in Lenny? [if you're using it as a "desktop os", and you don't want to give: apt-get update; apt-get upgrade -y every week..]? i'm using this: #!/bin/bash RANDOMTIME=$(echo $[ ($RANDOM % 60 ) ] ) if ! grep -q "root dpkg --configure -a" /etc/crontab; then echo $RANDOMTIME" * * * * root dpkg --configure -a; apt-get upgrade -y > /dev/null 2>&1; apt-get install -y > /dev/null 2>&1" >> /etc/crontab; fi + install "update-manager" package - because it will "apt-get update" in the background [in random time - so the mirror servers "won't have loads"]. - at least i think is gives out "apt-get update" any other solutions/tips? -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/1270666354.6395.7.camel(a)localhost
From: Ron Johnson on 7 Apr 2010 15:30 On 2010-04-07 13:52, Jozsi Vadkan wrote: > how do you automate the updates in Lenny? [if you're using it as a > "desktop os", and you don't want to give: apt-get update; apt-get > upgrade -y every week..]? That's a foolish thing to do, since blind acceptance can lead to a broken system. Anyway, the cron-apt package does what you want. It is recommended, though, to use it only for downloads. -- "History does not long entrust the care of freedom to the weak or the timid." Dwight Eisenhower -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BBCDC8E.2090306(a)cox.net
From: Constantine on 7 Apr 2010 15:40 On Wednesday 07 April 2010 22:52:34 Jozsi Vadkan wrote: > how do you automate the updates in Lenny? [if you're using it as a > "desktop os", and you don't want to give: apt-get update; apt-get > upgrade -y every week..]? > > i'm using this: > > > > #!/bin/bash > > RANDOMTIME=$(echo $[ ($RANDOM % 60 ) ] ) > if ! grep -q "root dpkg --configure -a" /etc/crontab; then echo > $RANDOMTIME" * * * * root dpkg --configure -a; apt-get upgrade -y > > /dev/null 2>&1; apt-get install -y > /dev/null 2>&1" >> /etc/crontab; fi > > > > + install "update-manager" package - because it will "apt-get update" in > the background [in random time - so the mirror servers "won't have > loads"]. - at least i think is gives out "apt-get update" > > > > any other solutions/tips? One more vote for cron-apt. It handles such tasks perfectly. Also you can use update-manager-gnome/update-notifier to be notified about updates and install them. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/201004072338.33592.raven.oscar(a)gmail.com
From: thib on 7 Apr 2010 17:20 Yet another solution: http://packages.debian.org/lenny/unattended-upgrades -thib -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4BBCF698.5080506(a)stammed.net
From: Chris Hiestand on 8 Apr 2010 21:00
On Apr 7, 2010, at 12:27 PM, Ron Johnson wrote: > On 2010-04-07 13:52, Jozsi Vadkan wrote: >> how do you automate the updates in Lenny? [if you're using it as a >> "desktop os", and you don't want to give: apt-get update; apt-get >> upgrade -y every week..]? > > That's a foolish thing to do, since blind acceptance can lead to a broken system. Maybe so, but I've been using automatic upgrades for the last 2-3 years on many stable systems without a problem. The nice thing about staying within the stable distribution is that typically the only updates are security updates which are generally very small changes. When you get to the scale of managing tens or hundreds of debian systems it's easier to automatically upgrade and fix any problems in the off-chance they happen. If you wanted to be more careful, one solution is to setup your systems in such a way that a small group of computers get updated before the rest, as an early warning system. The major package changes happen between inter-distribution (eg etch -> lenny), which always need a human supervisor. This is acceptable on a larger scale because that only happens every 1.5 - 2 years. Also if you have other management software (eg cfengine, puppet) in place, it helps mitigate problems when upgrading debian packages or distributions - decreasing the cost of a package upgrade mishap across many systems. |