Thanks for your response. My experience is, in general, that even
long-idle AFS mounts work fine across NAT; the only time this has caused a
problem is when there's a documented drop in connectivity between the
firewall and the AFS server.
I'll work on fs checks and fs flush next time this happens
Andrew Perrin <[EMAIL PROTECTED]> writes:
> I'm running debian woody on a home machine that's behind an NAT
> masquerader (also woody). The home machine runs the OpenAFS client
> to connect to the UNC campus's AFS shared directory space. Generally
> this works fine, but there's one situation that c
2 matches
Mail list logo
