[CentOS] LS command bizzare behavior
Dan Hyatt
dhyatt at dsgmail.wustl.eduMon Sep 22 20:12:07 UTC 2014
- Previous message: [CentOS] LS command bizzare behavior
- Next message: [CentOS] LS command bizzare behavior
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
So how do I fix it. We actually have a widespread problem with files and directories "disappearing"... as it is one user in particular it might be pilot error, but it might be this. Because this is happening to two competent users. On 9/22/2014 1:11 PM, Keith Keller wrote: > On 2014-09-22, Frank Cox <theatre at melvilletheatre.com> 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 >
- Previous message: [CentOS] LS command bizzare behavior
- Next message: [CentOS] LS command bizzare behavior
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list