See, the real problem wasn't rolling out an update to 100 servers. The real Problem was redhat releasing an untested piece of software to my satellite server, which then gets automatically installed whenever a new system kickstarts. The problem would be nullified, if inside the satellite server I could roll-back the rhncfg.* packages in the rhel-i386-ws-3-u4 net tools channel, but unfortunately, I cannot do this. On 3/30/05 12:39 PM, "Pettit, Paul" <ismanager@xxxxxxxxxxx> wrote: >> Michael Halligan >> >> Thanks redhat, you have assured that I am moving my >> infrastructure to SuSE & Zenworks, and that our future plans, >> as well as mine as a consultant, will not include a software >> distribution with the word HAT in it. >> >> ------------------- >> Michael T. Halligan > > Not the first and won't be the last. > > I do have to comment on the fact that you rolled out that update to 100 > servers before spot checking it. That was rather dumb IMHO. I mean if it > had been 2 or 4 servers then oh well but 100?! Should have done a test > on 1 or 2 just incase. Shame on you bud. > > Paul Pettit > CTO and IS Manager > Consistent Computer Bargains Inc. > > I've heard it said that the proof of lunacy is when you repeat the same > steps expecting different results. I say it's proof that you're a > Microsoft user. - comment by deshi777 on experts-exchange.com -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
