Dave B wrote: > our experience is usually different. When afs is not running, it's almost due > to a problem where no matter how many times one tries to restart the client, > the client service won't restart. These issues, which usually occur after > updating the client, are usually related to cache size issues on 32-bit > windows. So, other than afscreds returning an error that the service is not > running, afscreds really isn't the right answer here (usually, we can use > pslist or look at the services on the computer remotely).
Why is the service not starting? What error did the service manager log in the windows application event log? What error was reported in afsd_init.log?
smime.p7s
Description: S/MIME Cryptographic Signature
