[krbdev.mit.edu #8555] gss_krb5_ccache_name has no effect

[Greg Hudson via RT]

We have automated tests which use gss_krb5_ccache_name(), as well as 
some uses of it elsewhere in our tree, so I don't think it's uniformly 
broken.  Is your program multi-threaded?  gss_krb5_ccache_name() sets a 
per-thread variable, so it won't have an affect on GSS calls made by 
other threads.

In kg_sync_ccache_name(), you are correct that err is never set prior to 
the if statement, but the condition is on !err, so it always fires.  The 
developer who originally wrote that code preferred to use an "if ladder" 
style of flow control where all of the mainline code occurs within an 
"if no error has occurred yet" conditional.  We no longer use that 
pattern, but there are traces of it here and there including that 
function.