On Thu, 2008-04-10 at 12:35 -0400, Mark Haney wrote: > Aaron Konstam wrote: > > On Thu, 2008-04-10 at 08:06 -0400, Mark Haney wrote: > >> Patrick O'Callaghan wrote: > >>> On Wed, 2008-04-09 at 17:15 -0400, Joe Smith wrote: > >>>> Mark Haney wrote: > >>>>> And yes /bin/ls --color=tty hangs. In fact, I changed it to color=auto > >>>>> and THAT hangs as well. I changed the ls alias to be just 'ls' and that > >>>>> works fine for all directories that were hanging before. But now, ls > >>>>> -l hangs too. Man, this is weird. > >>>> Both colorizing the names based on the file type and getting the file > >>>> metadata for a long listing require reading each file's inode, whereas > >>>> 'ls' showing only the name requires only reading the directory data. > >>> If that's the case then "ls -l" should also hang. Does it? > >>> > >>> poc > >>> > >> ls -l /does/ hang in those cases, /with/ and /without/ the color option. > >> However, the hang is different. With ls --color=tty the hang locks > >> the entire ssh session. Whereas I can CTRL+C out of the ls -l hang. > >> > >> So you think this is inode/disk related? > > Since this happens in only one directory I would think it is the > > directory that is the problem. > > > > Try: echo * > > in that directory and see what you get. > > > > It /doesn't/ happen in only one directory. It just happens that I'm > doing my testing in one particular directory. I would still run: echo * and see what it returns. echo * usually returns a compact version ls *. -- ======================================================================= Machines certainly can solve problems, store information, correlate, and play games -- but not with pleasure. -- Leo Rosten ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx
