Path: utzoo!attcan!uunet!samsung!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!news.funet.fi!fuug!mjolner!newshost!jnp From: jnp@tnds05.tele.nokia.fi (J|rgen N|rgaard) Newsgroups: comp.sys.apollo Subject: Peculiar behaviour of "ls //" Message-ID: Date: 28 Jan 91 13:03:56 GMT Sender: news@mjolner.tele.nokia.fi Distribution: comp Organization: Nokia Telecommunications Lines: 61 Hi, [Apollo DN3500, DN2500, SR10.1, SR10.2 BSD4.3, ethernet] Can anybody explain why our network directory exhibits a rather strange behaviour ? What happens is that a command like, say, "ls //" takes rather long time to complete whereas "time ls //" is very fast. First "ls //": bash# date; ls // ; date Mon Jan 28 14:34:55 EET 1991 .bash_history* .emacs* andromeda/ dionysos/ kronos/ .bash_login* afrodite/ atlas/ kirke/ mjolner/ Mon Jan 28 14:39:18 EET 1991 bash# That is 5 minutes to complete "ls" (amazing indeed !) Next "time ls //": bash# time ls // .bash_history .emacs andromeda dionysos kronos .bash_login afrodite atlas kirke mjolner 0.5 real 0.0 user 0.1 sys bash# Which is acceptable. What is the difference between the two in the first place ? And why does it happen at all ? I don't see any clue to this at the moment. [Further details: bash# time ls //atlas .cshrc domain_examples patch sys5.3 tmp bin etc rc.local sysboot tosi-isode ....... 52.8 real 0.0 user 0.0 sys bash# bash# time ls //atlas/bsd4.3 bin etc usr 0.4 real 0.0 user 0.0 sys bash# ] -- ORIGIN '~jnp/stdDisclaimers'; [[--- Regards, J|rgen N|rgaard ('|' is '\o{}' in \LaTeX{}) | | e-mail: jnp@tele.nokia.fi || Telephone: <..>-358-0-511-5671 | | mail: Nokia Telecommunications, PL 33, SF-02601 Espoo Finland ---]]