We have a system in the field that shows a symptom that I have not seen before. If I type a command, e.g. "sin", the 
command executes immediately; however, after the list of processes has been printed, there is a long period, perhaps 15 
to 20 seconds, where nothing happens before the command prompt returns. Other commands, such as "ls", behave similarly. 
It seems that something is holding up the command's exit, but what it is is hard to say.

If anyone has any insight into this, I'd appreciate hearing about it.

Thanks,

Kevin