The test suite doesn't wait long for the gss-server process to start 
accepting connections.  At IETF-60, in the hotel room with rather 
mediocre network access, resolving my own hostname takes a while (and 
I'm on a Mac, so no caching configured).  This means the gss-server 
process can take a long time to figure out its own service principal 
name.  By the time it does, some of the tests have already failed.

Possible fix: Very long delay before starting client processes.

Suggested fix: Have the server output a "ready" message when it's 
listening for incoming connections, and have the test suite permit a 
long delay for that message, but continue on as soon as the message is 
seen.

Ken