Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gd_nfragments(3) [debian man page]

gd_nfragments(3)						      GETDATA							  gd_nfragments(3)

NAME
gd_nfragments -- retrieve the number of format specification fragments in a dirfile SYNOPSIS
#include <getdata.h> int gd_nfragments(const DIRFILE *dirfile); DESCRIPTION
The gd_nfragments() function queries a dirfile(5) database specified by dirfile and returns the total number of parsed format specification fragments in the database. The dirfile argument must point to a valid DIRFILE object previously created by a call to gd_open(3). RETURN VALUE
Upon successful completion, gd_nfragments() returns the total number of format specification fragments which are present in the dirfile. On error, gd_nfragments() returns zero and sets the dirfile error to a non-zero value. Possible error values are: GD_E_BAD_DIRFILE The supplied dirfile was invalid. The dirfile error may be retrieved by calling gd_error(3). A descriptive error string for the last error encountered can be obtained from a call to gd_error_string(3). SEE ALSO
dirfile(5), gd_fragmentname(3), gd_include(3), gd_open(3), gd_parent_fragment(3) Version 0.7.0 21 July 2010 gd_nfragments(3)

Check Out this Related Man Page

gd_nfields(3)							      GETDATA							     gd_nfields(3)

NAME
gd_nfields -- report the number of fields in a dirfile SYNOPSIS
#include <getdata.h> unsigned int gd_nfields(DIRFILE *dirfile); DESCRIPTION
The gd_nfields() function queries a dirfile(5) database specified by dirfile and returns the number of fields defined in the database. No- tably, this count does not include /META fields. The dirfile argument must point to a valid DIRFILE object previously created by a call to gd_open(3). RETURN VALUE
Upon successful completion, gd_nfields() returns the number of defined fields in the dirfile. On error, it returns zero and sets the dirfile error to a non-zero error value. Possible error values are: GD_E_BAD_DIRFILE The supplied dirfile was invalid. The dirfile error may be retrieved by calling gd_error(3). A descriptive error string for the last error encountered can be obtained from a call to gd_error_string(3). SEE ALSO
dirfile(5), gd_open(3), gd_error(3), gd_error_string(3), gd_field_list(3), gd_nfields_by_type(3), gd_nmfields(3), gd_nvectors(3) Version 0.7.0 16 July 2010 gd_nfields(3)
Man Page

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

fragments in Solaris 8

When discussing inodes and data blocks, I know Solaris creates these data blocks with a total size of 8192b, divided into eight 1024b "fragments." It stores data in "contiguous" fragments and solaris doesn't allow a file to use portions of two different fragments. If the file size permits, then the... (4 Replies)
Discussion started by: manderson19
4 Replies

2. UNIX for Dummies Questions & Answers

how to copy update without interactive

Dear, How to copy update without interactive confirmation? I am using #cp -Rfu dirfile dirfile But the interactive confirmation still exist. Thank you. (0 Replies)
Discussion started by: blesets
0 Replies

3. Programming

fifo

Dear friends i'm want to implement a program which one file is split into fragments by the server (by some random size) and sent to some processes, so these processes get randomly the fragments of the original file from the server, then the downloader randomly connects to some of these processes... (0 Replies)
Discussion started by: saman_glorious
0 Replies