<<On Thu, 18 Mar 1999 22:49:10 +0800, Peter Wemm <pe...@netplex.com.au> said:
> AMD is easy to upset, and that's bad because it's holding a mountpoint in / > (ie: /host) which often gets hit by every single getcwd() call when it > gets a lstat("/host"...) or whatever. I think this is the single largest > source of load on the amd process. > IMHO, /host needs to move down a level to get it out of the way of > getcwd(). NFS mounts should probably move away from / as well, as they > cause traffic on each getcwd(). `/host' is non-standard. The Standard Configuration is `/net' is the directory simulated by amd and `/a/${hostname}/root' is where amd mounts the directory tree. This is done specifically to avoid getcwd wedgitude. The example we ship would sorely puzzle anyone who is experienced running a Standard Configuration amd. My machine has, throughout its entire history, had `/home' simulated by amd. I have literally *never* had amd hose my configuration (and I would know it fast since both mail and Web service would break). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message