[OpenAFS-devel] stat bug?

[Neulinger, Nathan]

You can also just do "find X -follow", although that'll follow symlinks as
well.

Here's a thought - what if the number were too high? i.e. suppose it instead
returned a count of ALL entries in the dir. It wouldn't really be correct,
but would the behavior be more useful?

-- Nathan

> -----Original Message-----
> From: Nickolai Zeldovich [mailto:kolya@MIT.EDU]
> Sent: Tuesday, August 21, 2001 11:47 AM
> To: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] stat bug?
> 
> 
> > what would be the right way to fix this?  tell find not to 
> use optimizations
> > or have afs return a 'more correct' link count?
> 
> GNU find has a flag exactly for this purpose (-noleaf).  Fixing it
> would be nice, but right now the cache manager simply passes the
> file server's LinkCount as nlink..  In order to get a more correct
> link count it would have to FetchStatus every file in that directory
> to count symlinks + directories (and then maybe readlink to be more
> accurate..)
> 
> (I guess the fileserver could potentially keep such state, and use
> one of the spares in AFSFetchStatus for this, but I haven't seen
> this problem affect anything but GNU find, so doing this might be
> overkill..)
> 
> -- kolya
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>