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).
On Wed, Oct 14, 2009 at 07:02:40PM -0400, David R Boldt wrote: > > It worries me that checking whether or not afsd_service.exe is running > > is one of the goals. It implies that you have a high enough incident > > rate where it is not that we have a problem to address that I may not > > be aware of. > > Determining whether or not AFS is actually running is always > one of our user support steps after confirming that other > more obvious things are not at fault. > > Almost always a simple reinstallation of OpenAFS solves > the issue when the client is not starting. Reinstallation > ends up solving perhaps 5-10% of our "can't access my files" > issues. > > > -- David Boldt > <[email protected]> > > > "If all economists were laid end to end, they would not reach a > conclusion." > --George Bernard Shaw > -- ******************************** David William Botsch Programmer/Analyst CNF Computing [email protected] ******************************** _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
