Albert Chin <[EMAIL PROTECTED]> wrote: ... > So, looks like we don't want STAT_STATVFS on this platform. Maybe we > should check for STAT_STATFS3_OSF1 first in m4/fsusage.m4 before > STAT_STATVFS?
Thanks for pursuing this. Unfortunately, that is too risky. statvfs is the preferred interface, and other systems have both. Since Tru64 UNIX 5.1 is not exactly mainstream, and the goal here is to work around their statvfs bug, I'm willing to add to this exclusion list in fsusage.m4: #if defined __GLIBC__ && !defined __BEOS__ Do not use statvfs on systems with GNU libc, because that function stats all preceding entries in /proc/mounts, and that makes df hang if even one of the corresponding file systems is hard-mounted, but not available. statvfs in GNU libc on BeOS operates differently: it only makes a system call. #endif E.g., add these lines after that block: #ifdef TRU64 "Do not use Tru64's statvfs implementation" #endif Does that solve the problem for you? _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
