Hi,

I have just killed a 'make install' of shells/standalone-tcsh (which 
is supposed to install a statically-linked /bin/tcsh) after the 
spawned find(1) process had taken up 20 mins.

The build machine is mac68k with a few GBytes worth of NetBSD sources 
and other data mounted via NFS (fixed as well as amd(8)). Apparently, 
the find(1) process kicked off from mk/bsd.pkg.check.mk feels it has 
to scan _everything_ below ${PREFIX}, which in the case of the 
package mentioned is "/".

Apart from the amount of time needed, scanning network shares for 
changes is pointless in this context, since there may be legitimate 
changes entirely unrelated to pkgsrc installation. From a quick scan 
of the NetBSD find(1) man page, I do not see an easy way of teaching 
find(1) to stay away from network volumes.

What can be done, short of killing amd and taking the machine off the network?

	hauke


-- 
/~\  The ASCII Ribbon Campaign                    Hauke Fath
\ /    No HTML/RTF in email	        Institut für Nachrichtentechnik
  X     No Word docs in email	                  TU Darmstadt
/ \  Respect for open standards              Ruf +49-6151-16-3281