search for: statvfs64

...ail-compact". The point I was complaining about with "X free - not X+1" was that the suggested changes cap the values returned in f_files, f_ffree, and f_favail at UINT32_MAX. If a 32-bit statvfs() returns UINT32_MAX for any of these values when a simultaneous 64-bit statvfs() or a statvfs64() would set one or more of those values to a larger value (I don''t care if it is +1, *2, or *1000), I think we have a problem. >The "X not X-1" is, on the other hand, to be taken very seriously. I >cannot claim to have free space if I haven''t, and that''s...

trying to compile 2.2.3a on solaris 8 and getting the following: Is it supported on sol 8? after typing configure and after many lines i get: -----much deleted------ ecking how to get filesystem space usage checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs...

...in advanced. /opt/Samba/3.0.21a/sbin> ./nmbd -D & [1] 544860 oldpetes: root] /opt/Samba/3.0.21a/sbin> exec(): 0509-036 Cannot load program ./nmbd because of the following errors: 0509-130 Symbol resolution failed for nmbd because: 0509-136 Symbol statvfs64 (number 134) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol opendir64 (number 169) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol closedir64 (number 170) is not exported from...

...s work). The issue is that large filesystems can cause EOVERFLOW on statvfs() calls. This behavior is documented in the statvfs(2) man page, but I think we can do better. The problem was initially reported against ZFS, and my first fix was to zfs_statvfs(). But the VFS_STATVFS routines only see a statvfs64, so they have no way to tell if they''re about to cause EOVERFLOW. This means that they would always have to limit themselves to 32-bit values, which seems like the wrong direction for a fix. The change detects when cstatvfs32 is about to return EOVERFLOW, and attempts to rescale the stat...

...c number to a 'static const char' is > fine with me, please don't use a macro though. I do not like macros either. However, how should I remove magic numbers from | } else if (Name == "\1stat64" || | Name == "\1lstat64" || | Name == "\1statvfs64" || | Name == "\1__isoc99_sscanf") { without using a macro? Something like | } else if (Name[0] == llvm_asm_prefix && Name.slice(1, 0) == "stat64" || | Name[0] == llvm_asm_prefix && Name.slice(1, 0) == "lstat64" || |...

Hi! I am trying to install samba 2.2 on a Sun and I'm getting this error: ./configure --prefix=/local --with-ssl checking how to get filesystem space usage checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs...

...issues section of the readme. I made the appropriate corrections and now I get this error msg: root@570a sbin]$./nmbd -D;./smbd -D exec(): 0509-036 Cannot load program ./nmbd because of the following errors: 0509-130 Symbol resolution failed for nmbd because: 0509-136 Symbol statvfs64 (number 134) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol opendir64 (number 169) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol closedir64 (number 170) is not exported from...

Has any of you compiled the lastest Samba 3.0 RC2 on Sparc Solaris 9? Any idea about the warning messages in the text attachment ? Thanks.

Hello all. I'm trying to create the rpm for Samba 2.2.5. I haven't uninstalled the other version as we are using it. I got the tar.gz from the Samba web site. I type # sh makerpms.sh and this is what I get this @ the end: checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs...

...X 5.2, and installing, I get the following running testparm or smbstatus :- [WMSTRAIN:root]/opt/Samba/3.0.21b/bin> smbstatus exec(): 0509-036 Cannot load program smbstatus because of the following errors: 0509-130 Symbol resolution failed for smbstatus because: 0509-136 Symbol statvfs64 (number 115) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol opendir64 (number 145) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol closedir64 (number 146) is not exported from...

NFS server (b39): bash-3.00# zfs get quota nfs-s5-s8/d5201 nfs-s5-p0/d5110 NAME PROPERTY VALUE SOURCE nfs-s5-p0/d5110 quota 600G local nfs-s5-s8/d5201 quota 600G local bash-3.00# bash-3.00# df -h | egrep "d5201|d5110" nfs-s5-p0/d5110 600G 527G 73G 88% /nfs-s5-p0/d5110

On Nov 18, 2009, at 10:17 AM, Timo Juhani Lindfors wrote: > Hi, > > llvm, clang and llvm-gcc contain numerous references to 1, '\1', > '\01', '\001', "\01" and "\01foo". This makes it difficult for one to > find all occurences of this prefix character and lacks a central place > where the prefix could be documented. (See for example

hi, I have a problem compiling samba 2.2.0 on mandrake 8.0 first: when I want to compile with pam I get the folowing error ------------------------------- checking how to get filesystem space usage checking statvfs64 function (SVR4)... (cached) yes checking checking if large file support can be enabled... yes checking whether to support ACLs... no checking configure summary configure: error: summary failure. Aborting config ------------------------------- what can I do about it? When I compile without pam, I g...

...edition: I'm trying to create the rpm for Samba 2.2.5. I haven't uninstalled the other version as we are using it. Once I get thinks right, will I have to # rpm -e <old rpm>, or can I # rpm -U <new rpm> from 2.2.3.a? Here is the error message and what came before: checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs...

...9; discards qualifiers from pointer target type Compiling lib/system.c lib/system.c: In function `sys_readdir': lib/system.c:331: warning: return from incompatible pointer type Compiling lib/fsusage.c lib/fsusage.c: In function `sys_fsusage': lib/fsusage.c:127: warning: passing arg 2 of `statvfs64' from incompatible pointer type Compiling tdb/tdbutil.c tdb/tdbutil.c: In function `tdb_chainlock_with_timeout': tdb/tdbutil.c:46: warning: passing arg 1 of `tdb_set_lock_alarm' discards qualifiers from poi nter target type Best regards, Kees

...send 0.00 87 getdents 0.75 1727 fstat64 0.00 31 lseek64 0.00 8 lstat64 0.48 11809 stat64 0.09 170 93 statvfs64 0.00 7 acl 0.00 8 8 ----- ----- ----- ----- Total 1.42 15750 121 sysconf(_SC_OPEN_MAX) ............................................................

.../opt/Samba/3.0.21a/sbin> ./nmbd -D & [1] 544860 oldpetes: root] /opt/Samba/3.0.21a/sbin> exec(): 0509-036 Cannot load program ./nmbd because of the following errors: 0509-130 Symbol resolution failed for nmbd because: 0509-136 Symbol statvfs64 (number 134) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol opendir64 (number 169) is not exported from dependent module /usr/lib/libc.a(shr.o). 0509-136 Symbol closedir64 (number 170) is no...

Hi, llvm, clang and llvm-gcc contain numerous references to 1, '\1', '\01', '\001', "\01" and "\01foo". This makes it difficult for one to find all occurences of this prefix character and lacks a central place where the prefix could be documented. (See for example http://llvm.org/bugs/show_bug.cgi?id=5480 ) How about adding a #define for this prefix?

Hi, I'm trying to get Samba-2.1.0-prealpha compiled but I always get stuck at the following error message: root@pc2:/usr/src/samba-2.1.0-prealpha/source > make Using LIBS = -lcrypt Linking bin/rpcclient rpcclient/rpcclient.o: In function `process': rpcclient/rpcclient.o(.text+0x4c3): undefined reference to `wait_keyboard' collect2: ld returned 1 exit status make: ***

...normal scan, which took .0028 seconds, followed by some log writing (which took about .0042 seconds per line!) This was then followed by stats for the ls (which is something of an ls -l) which took .2799 seconds, ~96 times the getdents time, and a statvfs to get the disk space free 4.0985 statvfs64(".", 0xFFBEEFD0) There were 184 entries in the directory I used, 6096 bytes, and that gives a readdir speed of about 1.4 MB/S or 44 K-entries/S for a small directory. Big ones get slower as a function of indirect blocks used, so there will be a step-function in the speed yo...