Bug 1369 - gss-cleanup.sh sometimes fails on fast machines
Summary: gss-cleanup.sh sometimes fails on fast machines
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Miscellaneous (show other bugs)
Version: 4.7p1
Hardware: SPARC Solaris
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords:
Depends on: 1242
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-25 10:47 AEST by David Leonard
Modified: 2008-04-04 10:01 AEDT (History)
1 user (show)

See Also:


Attachments
slow down gss-cleanup.sh (517 bytes, patch)
2007-09-25 10:47 AEST, David Leonard
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description David Leonard 2007-09-25 10:47:58 AEST
Created attachment 1361 [details]
slow down gss-cleanup.sh

It looks like the gss cred deletion code runs after the client has disconnected. Meaning, there is a race condition in regress/gss-cleanup.sh. When the first client disconnects, the second looks to see if the cleanup has finished. In the mean time, the first server process may not have completed.

This appeared on some of my faster boxes, I was getting occasional failures with gss-cleanup.sh, saying that the cred cache was left behind, but I couldn't find it. Adding a 'sleep 1' seems to have helped a lot.
Comment 1 Darren Tucker 2007-09-25 12:15:03 AEST
Thanks, but our regress tests don't have a gss-cleanup.sh :-)
Comment 2 David Leonard 2007-09-25 19:23:02 AEST
oops!! silly me.. :)
well, if you ever need some gss regression tests I have some here at http://rc.quest.com/viewvc/openssh/trunk/openssh/regress/
Comment 3 Damien Miller 2008-04-04 10:01:05 AEDT
Close resolved bugs after release.