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]
