Re: apt upgrade
Norbert Tretkowski said: > * Ivan Adams wrote: >> My quiestion is how I can avoid that kind of problems when on some >> Debian I have that kind of apt scripts. > > Disable those kind of scripts, and use apt-cron to let you inform by > mail when updates are available. I'de also reccomend running apt-cacher as you get: fast local updates, your packages are as current as the remote servers, you don't have to wait to sync. uses less space then a full mirror. saves lots of bandwidth for you and for the debian servers. With 10 clients running off 1 apt-cacher server you should see 9/10 bandwidth savings. -- --Luke CS Sysadmin, Montana State University-Bozeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt upgrade
* Ivan Adams wrote: > My quiestion is how I can avoid that kind of problems when on some > Debian I have that kind of apt scripts. Disable those kind of scripts, and use apt-cron to let you inform by mail when updates are available. Norbert -- personal - http://www.inittab.de/ debian - http://people.debian.org/~nobse/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt upgrade
[ cc-ed back to debian-isp ] On Tue, Sep 07, 2004 at 09:21:20PM +0300, Ivan Adams wrote: > but how can i understand when there have critical backdoor in some of my > packets in all Debians and need upgrade! subscribe to the security alert lists and upgrade when advised. you're trying to automate something which should not be automated. > RedHat have client who updates all critical problems automaticaly (or from > Web, but you just say update and that's). I mean how in RedHat all > administrators are sure that their linux is fine after update! if that's all you want then run stable and update from security.debian.org - you'll just get the security updates, which are infrequent. you might occasionally run into the same problem but, given that the security updates are a) backports rather than new versions and b) rare, it's nowhere near as likely as with unstable or testing. with unstable or testing, updated packages will be many and frequent - usually dozens every day. the more packages, the more likely that one of them will need to ask a question, or have a new config file which is incompatible with the previous version, or some other show-stopping problem. > Is that one step back for Debian !? no. i doubt that it works perfectly for RH either. it's not a task that can be completely automated. upgrading requires a skilled person in control of the process. and if you run unstable on production servers (as i do), then you really ought to test all upgrades on other servers or workstations first. the last thing you need is to discover that an upgraded apache or postfix or squid or whatever is broken AFTER you've upgraded it on the server that your users depend upon. craig -- craig sanders <[EMAIL PROTECTED]> The next time you vote, remember that "Regime change begins at home" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt upgrade
On Sun, Sep 05, 2004 at 10:58:40PM +0300, Ivan Adams wrote: > I used script with apt-get upgrade -y on Debian 3.0 Woody in crond. > Everything was ok when one day call me for problem in that linux. When I > enter in console I saw in logs that previous day he was apt-get upgrade -y > and upgraded squid. The problem was the new version of squid has one more > option in squid.conf, and i have to append the file and done the job by hand. > > My quiestion is how I can avoid that kind of problems when on some Debian I > have that kind of apt scripts. write an expect (or similar) script. which requires knowing in advance what questions you're going to be asked - which, of course, you don't because the questions will change for every upgrade. now you know one of the many reasons why running 'apt-get upgrade' from cron is a bad idea. even if there are no packaging errors, you're occasionally going to get hit by something like this. upgrades really need someone competent watching them anyway. they should never be completely automated. craig -- craig sanders <[EMAIL PROTECTED]> The next time you vote, remember that "Regime change begins at home" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt upgrade
On Sun, 5 Sep 2004 22:58:40 +0300, Ivan wrote in message <[EMAIL PROTECTED]>: > Hi, > I used script with apt-get upgrade -y on Debian 3.0 Woody in crond. > Everything was ok when one day call me for problem in that linux. > When I enter in console I saw in logs that previous day he was apt-get > upgrade -y > and upgraded squid. The problem was the new version of squid has one > more option in squid.conf, and i have to append the file and done the > job by hand. > My quiestion is how I can avoid that kind of problems when on some > Debian I have that kind of apt scripts. ..'apt-get -suy upgrade && apt-get -uy upgrade '? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
apt upgrade
Hi, I used script with apt-get upgrade -y on Debian 3.0 Woody in crond. Everything was ok when one day call me for problem in that linux. When I enter in console I saw in logs that previous day he was apt-get upgrade -y and upgraded squid. The problem was the new version of squid has one more option in squid.conf, and i have to append the file and done the job by hand. My quiestion is how I can avoid that kind of problems when on some Debian I have that kind of apt scripts. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
