"This should not happen"... Never confuse theory with practice. In Software development, theory and practice appear identical. (BT,DT)
In Systems Integration and Application Production Support you quickly learn that theory and practice are seldom within the same galaxy much less the same solar system. (BT,DT) I've done enough problem determination within BOTH environments... (chuckles) (Draws on memory) Running an IBM labspace I had three AIX servers for supporting testing of an application that required SNA support. I also owned the delegated DNS subdomain so it was up to me to recommend names. One server handled functional testing, the second was for system testing and the final one for "user" testing. I named them flog, flail and flaunt. (The SNA gateway was named "phlegm", BTW, instead of "snaat".) In various places, beyond this, I have learned that "UAT" seems to stand for "User Avoided Testing". I've also worked w/ Tandem guys who throw around claims like 5 nines... and had the systems _I_ supported insulted as 9 fives servers. (shrugs) So I have a LOT of practice learning how systems DO NOT WORK AS EXPECTED. To paraphrase Patton's Law for this milieu... "No Plan Survives Contact With Reality". -soup On Wed, Apr 18, 2018 at 3:01 PM, Christian Borntraeger < [email protected]> wrote: > On 04/18/2018 03:36 PM, Dave Jones wrote: > > Hello, gang. > > > > I have a very simple bash script that runs a trivial data collection > > task, and then does a Linux "sleep im" to wait a minute before running > > the data collection task again. Under very high CPU loads (> 90%) I have > > noticed that the "sleep" command does not seem to wake up after one > > minute but instead wakes up 15 to 20 minutes later. This is on a Red Hat > > 6.9 guest running under z/VM 6.4 on a z12 box. > > > > I would like to buy a clue here if I could. > > This should not happen, even under load. Is this really the sleep that > does not > wakeup or is maybe the following stuff not getting access to the data? > Have you > tried with "set -x" in the bash script to see what commands bash is > executing? > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- John R. Campbell Speaker to Machines souperb at gmail dot com MacOS X proved it was easier to make Unix user-friendly than to fix Windows "It doesn't matter how well-crafted a system is to eliminate errors; Regardless of any and all checks and balances in place, all systems will fail because, somewhere, there is meat in the loop." - me ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
