[OpenAFS-port-darwin] Using AFS home directories under Tiger

[It's SPAM filtered]

On Aug 22, 2005, at 11:45 AM, Chaskiel M Grundman wrote:


> --On Friday, August 12, 2005 06:21:23 PM -0400 Chaskiel M Grundman  
> <cg2v@andrew.cmu.edu> wrote:
>
>
>
>> can you run the following commands a
>>
>>
>
> It has been pointed out to me that I failed to include the relevant  
> commands. While I did send them to Ian personally, there apparently  
> exist some lurkers who are having similar problems and want to know:
>
> cmdebug <client>
> rxdebug <client> 7001 -rxstats
>
> Also, anyone reporting a finder/dock/dashboard/whatever hang should  
> determine (using ps) what the state of the hanging process is (U,  
> uninterruptable sleep, or R, running. aka spinning in usermode.  
> Either of these could result in the beachball cursor being displayed.)
>
>
>

I don't understand these commands.  I see ...

[rreitz@over rreitz]$ cmdebug -help
Usage: cmdebug -servers <server machine> [-port <IP port>] [-long] [- 
addrs] [-cache] [-help]
Where: -long   print all info
        -addrs  print only host interfaces
        -cache  print only cache configuration

Humm, what do you mean by <client>?  I tried ...

[rreitz@over rreitz]$ cat /var/db/openafs/etc/ThisCell
fnal.gov
[rreitz@over rreitz]$ cmdebug fnal.gov
cmdebug: can't resolve address for host fnal.gov.
[rreitz@over rreitz]$ egrep fnal.gov /var/db/openafs/etc/CellServDB
 >fnal.gov               #Fermi National Acclerator Laboratory
131.225.68.1                    #fsus01.fnal.gov
131.225.68.4                    #fsus03.fnal.gov
131.225.68.14                   #fsus04.fnal.gov
[rreitz@over rreitz]$ cmdebug fsus01.fnal.gov
[rreitz@over rreitz]$ cmdebug fsus03.fnal.gov
[rreitz@over rreitz]$ cmdebug fsus04.fnal.gov

Well, this isn't helpful.  Can you give an example?

I frequently get the spinning beach ball.  I'm not sure about your  
instruction for finding the state of the hanging process.  I see ...

[rreitz@over rreitz]$ ps aux | egrep -i afs
root       228   0.0  0.0    27444    200  ??  S    Sun05PM    
0:00.02 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       229   0.0  0.0    27444    200  ??  U    Sun05PM    
0:00.00 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       230   0.0  0.0    27444    200  ??  U    Sun05PM    
0:03.93 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       231   0.0  0.0    27444    200  ??  U    Sun05PM    
0:00.82 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       232   0.0  0.0    27444    200  ??  U    Sun05PM    
0:00.09 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       233   0.0  0.0    27444    200  ??  U    Sun05PM    
0:00.00 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       234   0.0  0.0    27444    200  ??  U    Sun05PM    
0:00.00 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       235   0.0  0.0    27444    200  ??  U    Sun05PM    
0:00.00 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
root       241   0.0  0.0    27572    200  ??  U    Sun05PM    
0:00.00 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons
rreitz     676   0.0  0.0    27800      4  p1  R+    8:15PM   0:00.00  
egrep -i afs

So all the afsd's look to be in state 'U', but currently AFS is  
working fine.

Thanks,
Randy Reitz