Sponsored Content
Full Discussion: df command documentation
Top Forums UNIX for Advanced & Expert Users df command documentation Post 302083846 by gfhgfnhhn on Tuesday 8th of August 2006 07:03:31 AM
Old 08-08-2006
i want to see the exact relation between
df command and fstatfs(2), mount(2), statfs(2), statvfs(2)
functions and fs(4), fstab(4) files
 

8 More Discussions You Might Find Interesting

1. Programming

AIX 3.2.5 Documentation

I'm looking for books or online documentation for writing device drivers for AIX 3.2.5. I've searched IBM's website and google and come up with next to nothing. There is plenty of information for 4.1 and above but virtually nothing for 3.2.5. I'm specifically interested in porting one of the... (2 Replies)
Discussion started by: cejoe
2 Replies

2. UNIX for Advanced & Expert Users

xargs documentation or tutorial?

Can anybody please forward me a good xargs documentation or tutorial? - $nilesh (5 Replies)
Discussion started by: ynilesh
5 Replies

3. Solaris

Help with SunOS 5.8 documentation ?

Hi all. I have machine with SUN OS 5.8 but i don't have any documentation about that. where i can found any documentation about this OS? I have look in the sticky thread about Solaris in this forum, but can't found for the SUN OS 5.8. it's same with Solaris 10 or have major difference with... (4 Replies)
Discussion started by: urangkayo
4 Replies

4. Solaris

need LDAP documentation

Dear Members, 1- i need good documentation for LDAP installation, configuration 2- you recommeddation using LDAP under linux or solaris which is more easy for administration 3- is that possible to make integration between and LDAP and any email server like qmail (like windows active directory... (3 Replies)
Discussion started by: hosney00ux
3 Replies

5. Programming

libxml2 documentation

i need to read/write a xml file in c i found libxml2, but the documentation is awfull, im using google but i get most of vb, or c# results can anyone point me to a introduction tutorial? actually, any kind of documentation would be ok (just not the oficial The XML C parser and toolkit... (2 Replies)
Discussion started by: broli
2 Replies

6. Shell Programming and Scripting

Help with documentation

I have a list of file names Set Lst = "n02-z30-3x2drw-run1.log n02-z30-3x2drw-run2.log n02-z30-3x2drw-run3.log n02-z50-3x2drw-run1.log n02-z50-3x2drw-run2.log" So basically I have the files below n02-z30-3x2drw-run1.log n02-z30-3x2drw-run2.log n02-z30-3x2drw-run3.log ... (2 Replies)
Discussion started by: kristinu
2 Replies

7. HP-UX

HP-UX 10.20 Documentation

I'm trying to find the 10.20 documentation online. I found some stuff at g4u0420c.houston.hp.com but these are pretty poor scans some of them being almost unreadable - for example: http://g4u0420c.houston.hp.com/en/B1171-90076/B1171-90076.pdf which is a scan of a DRAFT version of the X... (9 Replies)
Discussion started by: perdrix
9 Replies

8. AIX

IBM Servers Documentation

Hello dear friends, I wanrt to document our servers configuration but have no Idea which softweare should I use for documenting server environment.. maybe anyone can suggest me which software should I use.. thanks in Advance (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies
STATVFS(3)						   BSD Library Functions Manual 						STATVFS(3)

NAME
fstatvfs, statvfs -- retrieve file system information LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/statvfs.h> int fstatvfs(int fildes, struct statvfs *buf); int statvfs(const char *restrict path, struct statvfs *restrict buf); DESCRIPTION
The statvfs() and fstatvfs() functions attempt to fill the structure pointed to by buf with file system statistics, but portable applications must not depend on this. Applications must pass a pathname or file descriptor which refers to a file on the file system in which they are interested. The statvfs structure contains the following members: f_namemax The maximum length in bytes of a file name on this file system. Applications should use pathconf(2) instead. f_fsid Not meaningful in this implementation. f_frsize The size in bytes of the minimum unit of allocation on this file system. (This corresponds to the f_bsize member of struct statfs.) f_bsize The preferred length of I/O requests for files on this file system. (Corresponds to the f_iosize member of struct statfs.) f_flag Flags describing mount options for this file system; see below. In addition, there are three members of type fsfilcnt_t, which represent counts of file serial numbers (i.e., inodes); these are named f_files, f_favail, and f_ffree, and represent the number of file serial numbers which exist in total, are available to unprivileged pro- cesses, and are available to privileged processes, respectively. Likewise, the members f_blocks, f_bavail, and f_bfree (all of type fsblkcnt_t) represent the respective allocation-block counts. There are two flags defined for the f_flag member: ST_RDONLY The file system is mounted read-only. ST_NOSUID The semantics of the S_ISUID and S_ISGID file mode bits are not supported by, or are disabled on, this file system. IMPLEMENTATION NOTES
The statvfs() and fstatvfs() functions are implemented as wrappers around the statfs() and fstatfs() functions, respectively. Not all the information provided by those functions is made available through this interface. RETURN VALUES
The statvfs() and fstatvfs() functions return the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate the error. ERRORS
The statvfs() function fails if one or more of the following are true: [EACCES] Search permission is denied for a component of the path prefix of path. [EFAULT] Buf or path points to an invalid address. [EIO] An I/O error occurred while reading from or writing to the file system. [ELOOP] Too many symbolic links were encountered in translating path. [ENAMETOOLONG] The length of a component of path exceeds {NAME_MAX} characters, or the length of path exceeds {PATH_MAX} characters. [ENOENT] The file referred to by path does not exist. [ENOTDIR] A component of the path prefix of Path is not a directory. The fstatvfs() functions fails if one or more of the following are true: [EBADF] fildes is not a valid open file descriptor. [EFAULT] Buf points to an invalid address. [EIO] An I/O error occurred while reading from or writing to the file system. SEE ALSO
statfs(2) STANDARDS
The statvfs() and fstatvfs() functions conform to IEEE Std 1003.1-2001 (``POSIX.1''). As standardized, portable applications cannot depend on these functions returning any valid information at all. This implementation attempts to provide as much useful information as is provided by the underlying file system, subject to the limitations of the specified data types. AUTHORS
The statvfs() and fstatvfs() manual page was originally written by Garrett Wollman <wollman@FreeBSD.org>. BSD
July 13, 2002 BSD
All times are GMT -4. The time now is 12:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy