Re: LS command bizzare behavior

[Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>]

On 2014-09-22, Frank Cox <theatre@xxxxxxxxxxxxxxxxxxx> wrote:
> On Mon, 22 Sep 2014 10:48:32 -0500
> Dan Hyatt wrote:
>
>> but we can vi the files, we can access them via other means if we know 
>> the name. Then once we have accessed them, LS now shows the files.
>
> Sounds like a caching issue to me.  After you have accessed the file, it's in the cache and you can see it.

More specifically, it sounds like a client-side caching issue.  I've
seen this happen on linux clients if I'm *really* fast on the trigger.


--keith

-- 
kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx


_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos