dirfile_uninclude (3) - Linux Manuals
dirfile_uninclude: remove a format file fragment from a dirfile
NAMEdirfile_uninclude --- remove a format file fragment from a dirfile
- int *dirfile_uninclude(DIRFILE *dirfile, int fragment_index, int del);
Before removing the specified fragment, all pending writes are flushed to RAW fields defined the the removed fragments. If del is zero, metadata changes will also be written to the removed fragments. If del is non-zero, the format file fragments will be deleted from disk, if possible. Regardless of the value of del, binary data files associated with RAW fields defined in the removed fragments will not be deleted. To delete these binary files, use dirfile_delete(3) before calling this function.
The primary format file (the fragment indexed by zero) cannot be removed from the dirfile.
RETURN VALUEOn success, dirfile_uninclude() returns zero. On error, -1 is returned and the dirfile error is set to a non-zero error value. Possible error values are:
- The supplied dirfile was opened in read-only mode.
- The library was unable to allocate memory.
- The supplied dirfile was invalid.
- The supplied fragment index was out of range, or an attempt was made to remove the primary format file.
- A temporary file could not be opened into which to write the metadata of a modified, removed fragment.
- The metadata of the fragment which included the removed fragment was protected from change.
- An error occurred while trying to flush or close a removed field. The dirfile error may be retrieved by calling get_error(3). A descriptive error string for the last error encountered can be obtained from a call to get_error_string(3). When finished with it, the DIRFILE object may be deallocated with a call to dirfile_close(3), even if the open failed.
NOTESThis function re-arranges the remaining format file fragments in some unspecified way, except for the primary fragment, which is guaranteed to remain at index zero. Callers which cache format file fragment indices must re-initialise their cache after calling this function.
Unlike dirfile_delete(3), fields which depend on fields removed by this function are not automatically updated, nor is any check made to ensure that this function does not leave fields with missing input fields. Because of this, a fragment inclusion may be easily moved from one fragment to another with a combination of dirfile_uninclude() and dirfile_include(3). However, if such checks are required, use dirfile_delete(3) to delete the fields defined in the removed fragments first.
SEE ALSOdirfile_delete(3), dirfile_include(3), dirfile_open(3), dirfile_reference(3), get_error(3), get_error_string(3), get_fragmentname(3), get_nfragments(3), dirfile(5), dirfile-encoding(5), dirfile-format(5)