Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!chip From: chip@chinacat.Unicom.COM (Chip Rosenthal) Newsgroups: comp.unix.internals Subject: Re: More on du(1) Keywords: funny sizes Message-ID: <1607@chinacat.Unicom.COM> Date: 5 Oct 90 00:15:49 GMT References: <384@pacer.UUCP> Organization: Unicom Systems Development, Austin, TX Lines: 23 In article <384@pacer.UUCP> davidb@Pacer.UUCP (David Barts) writes: >Followup-To: poster feych >This blocksize ends up embedded in du, and each system's du thinks that >the entire world uses the same size it does. In summary, avoid using >du on network directories--it does not give reliable information. Then the du is broke...which doesn't surprise me. I found several broken du's when testing the one I posted recently to comp.sources.misc. The tests were not run in networked environments - the problem was usually seen as botched double and triple indirection calculations. If your remote filesystem properly supports the statfs() system call then the du I posted will work since it uses statfs() to determine the filesystem block size. So, I'd expect it to be well behaved in most SysVish environments, even networked ones. -- Chip Rosenthal Unicom Systems Development, 512-482-8260 Our motto is: We never say, "But it works with DOS."