On Tue, Apr 01, 2003 at 10:24:47AM -0500, Ben Russo wrote: > However, I have 26 Enterprise subscriptions that my company paid a lot > of money for in order to use with production, commercial servers that > take care of customers who have SLA's and pay my company to take care > of their boxes. > > Yesterday was a nightmare, two security patches released and I am > scrambling to get up2date to successfully work, it would error out all > the time. I had scheduled outage windows during which I was supposed > to replace the kernel or glibc lib's and reboot specific servers and > they were late, had my customers pissed off. I raised this issue yesterday morning with my Red Hat contacts and the problem got quickly solved. I was seeing timeouts, but after that it was a bit sluggish but I got all the sendmail patches installed without significant issues. Since you're an Enterprise customer (and I'm not), did you phone Red Hat when you couldn't get through RHN? Red Hat was supposed to roll in more bandwidth last night. I haven't heard one way or the other if it happened. In the future, when planning scheduled updates, grab the packages without installing them. up2date -p will do this - it throws the rpms into /var/spool/up2date and then a subsequent update will get them from there. If you can't get to the network at all, you could at least manually update them from the rpms and then do an up2date -u later. There will undoubtably be times when the network is done, either because your own network is undergoing maintenance or because your ISP is busted. > It's one thing when it is "Free" and it is different when it is > labelled "Enterprise, Advanced Server" and you pay $800/year for it. > I'm not a happy customer. They realized that yesterday. Blocking up2date patch updates for paying customers was not in their plans. -- Ed Wilts, Mounds View, MN, USA mailto:ewilts@xxxxxxxxxx Member #1, Red Hat Community Ambassador Program
