Michal Hlavinka wrote:
> one our user has found ksh scripts are failing when system is under heavy 
> load.

This sounds like an issue I had in the past.  Under heavy disk usage 
(nightly backups, kernel compile, or "find / -user 1234 ..."), ksh93 
sessions would *sometimes*, not always, die with an "Alarm Clock" 
message:

.............cut here.........
ksh93$                  ## ksh93 prompt
Alarm Clock             ## ksh93 times out and logs me out?
$                       ## /usr/bin/sh prompt (Heirloom-sh)
.............cut here.........

At first I thought it was related to the ksh TMOUT variable.  I tried 
"TMOUT=0; export TMOUT" and then "unset TMOUT" in my $HOME/.kshrc but 
the problem persisted.  I also tried using ksh93 as my login shell 
instead of heirloom-sh (Bourne port from OpenSolaris) then running 
ksh93 after login.  Problem persisted.  

I was trying to gather more information before reporting the issue.  
Although it happened frequently it did not happen consistently.

I upgraded to Version JM 93t+ 2009-05-01 when it was available and 
the problem went away.


Issues occurred on Debian 4.0/x86 system with all the latest updates.

Affected versions:
------------------
ksh93t 2008-11-04
linux binary from AST and built from source on the Debian 4.0 system
ksh93$ echo ${.sh.version}
Version M 93t 2008-11-04

Debian 4.0 Intel x86 stock ksh93:
debian$ echo ${.sh.version}
Version M 1993-12-28 r

Slackware 12.2 Intel x86 stock ksh93:
slackware$ echo ${.sh.version}
Version M 1993-12-28 s+

I copied the Slackware binary to the Debian system.  I know this 
isn't the best thing to do but at the time I was just trying to get 
a stable ksh93 and the library dependencies were the same.


Unaffected:
-----------
ksh.2009-05-05.linux.i386 binary from AST web site
ksh93$ echo ${.sh.version}
Version JM 93t+ 2009-05-01

Since the binary ksh93t is working, I haven't bothered to build 
from source again.  Some day I will.

Probably an unrelated issue:  I also experienced a hang in ksh93 
(affected versions listed above) when running some pipelines, eg.: 
"env | sort" or "env | grep TMOUT".  While this was a consistent 
problem, I seem to remember seeing something in the change log about 
this being fixed.  For the record, the problem does not exist in 
Version JM 93t+ 2009-05-01.

I want to say thanks to all the AST folks.  ksh93 is great and 
I've moved to it as my default shell instead of bash.  

Keep up the good work!
--
scot

_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers

Reply via email to