"A month of sundays ago andy@ wrote:" > I would think the sol'n would be to make ls less nosey with symlinks. Possibly, but the symlinks in question are "brothers". They are sons of the same father dir, but ther eis no other connection. > I am not familar with the ls code at all, so I don't know what it is > doing. Since all the color stuff is somewhat new code to ls it should > not break anything to change it. No, it's very old code. I haven't changed my ls alias in seven years,. > I have just started reading the kernel-lists again so I have been very > quick on the delete key recently, so I don't know who orignally noticed > the color problem, but going back to the list may be the best way to > get the problem fixed, hopefully it is a simple patch to ls. Yes, thanks. I'll cc: this back (without your permission :-(). The real soluton however is to get automount not to run mount against a host it cannot ping! I may try modifying mount to exit fast with error too. New readers .. the --color=auto option to ls triggers automount to try and mount sibling dirs to the ls target dir. This is fatal when the sibling is aimed at a down host. The ensuing hung mount attempt blocks the ls return at least. Peter
