> then I set up a test environment and tracked it down to the printks. > odd until I saw reports of Linux hangs on /., the NTP newsgroup, and NANOG > here hung on New Year's Eve (luckily I wasn't on call). > RHEL 4 or 5 (with several Fedora and a couple of CentOS), one RHEL 4 server
:-( Out of a couple of dozen Linux systems, most running I think I still have the script on my test system (powered off at home right now) if you want it. I then started the above find command in another window, and the system crashed at the printk. I just wasn't sure how invasive the changes would be to keep it working.īTW: if you want to test, I reproduced this with a script that used adjtimex to set the flag to insert a leap second, set the clock to 23:59:59 UTC, watched the clock for a couple of seconds, and looped. Oh I definately like the message (I run NTP with a GPS receiver for stratum 1 accuracy in other words, I'm a time nut :-) ). > to users that a leap second has occurred. > No, I think the right thing to do is to keep the printks. It only seems to hang when the system is busy an idle system wouldn't hang, but running "find / -mount -type f | xargs cat > /dev/null" would cause it to hang at the first leap second attempt. I just thought it was odd until I saw reports of Linux hangs on /., the NTP newsgroup, and NANOG then I set up a test environment and tracked it down to the printks. :-( Out of a couple of dozen Linux systems, most running RHEL 4 or 5 (with several Fedora and a couple of CentOS), one RHEL 4 server here hung on New Year's Eve (luckily I wasn't on call). I thought you were reporting a hypothetical situation.
0 kommentar(er)
