This is a discussion on Kernel Update Breaks Script within the Linux General forums, part of the Linux Forums category; The script does it's update in 29 sec then the kernel was updated by yum update now script takes ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
The script does it's update in 29 sec then the kernel was updated by
yum update now script takes 3xx-5xx sec's. Rebooting to the old kernel does not clear problem. How can I find what was changed and isolate to the ??module?? causing the problem? We built a test box did not do yum it ran in 29 sec's then did yum on it and ugh 454 sec's. |
|
|||
|
whoha <noone@nowhere.com> wrote:
> The script does it's update in 29 sec then the kernel was updated by > yum update now script takes 3xx-5xx sec's. Rebooting to the old kernel > does not clear problem. How can I find what was changed and isolate to > the ??module?? causing the problem? I have no solution, but your problem seems to be a good argument against automated software updates. Yours, Laurenz Albe |
|
|||
|
In comp.os.linux.misc whoha <noone@nowhere.com>:
> The script does it's update in 29 sec then the kernel was updated by > yum update now script takes 3xx-5xx sec's. Rebooting to the old kernel > does not clear problem. How can I find what was changed and isolate to > the ??module?? causing the problem? > We built a test box did not do yum it ran in 29 sec's then did yum on > it and ugh 454 sec's. ?? How do you expect anyone to help you? You don't tell us which distro you are running? You don't tell us the error message and what is happening? *Please* "ESR's Howto ask smart questions" http://catb.org/~esr/faqs/smart-questions.html -- Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94) mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/' #bofh excuse 69: knot in cables caused data stream to become twisted and kinked |
|
|||
|
whoha wrote: > The script does it's update in 29 sec then the kernel was updated by > yum update now script takes 3xx-5xx sec's. Rebooting to the old kernel > does not clear problem. How can I find what was changed and isolate to > the ??module?? causing the problem? > > We built a test box did not do yum it ran in 29 sec's then did yum on > it and ugh 454 sec's. What was the old kernel version, and the new kernel version? |