strikes again.

Before I saw executables failing to run if started simultaneously, if
their pathnames contained the same symlink lying on Coda.

Now it is libraries - if two executables need libraries from the same
directory that needs symlink traversal on Coda, they tend to fail
with "cannot open shared object: No such file or directory" of some
library, when started in parallel.
They can use the libraries without problems when started at different
times.

(it concerns only libraries that are not already in use by some other
process, those are no problem).

I cannot tell absolutely for sure that it is symlinks that trigger the
problem, but it feels really the most probable. And at any rate it is
concurrent access to executable images that suffers.

Not really makes the system unusable, but is annoying while trying to
start multiple X-clients from scripts.

Server 5.3.15, client 5.3.15, both Pentium 100 on mostly idle 10Mbit LAN,
Linux x86, client kernel 2.4.14 with Coda module 5.3.15.
All files already in the cache.

Anyway - Coda is great. It is just the hardest last step - to make it
perfect :)

Cheers,
--
Ivan