1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212
|
.\" header.tmac. GetData manual macros.
.\"
.\" Copyright (C) 2016 D. V. Wiebe
.\"
.\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
.\"
.\" This file is part of the GetData project.
.\"
.\" Permission is granted to copy, distribute and/or modify this document
.\" under the terms of the GNU Free Documentation License, Version 1.2 or
.\" any later version published by the Free Software Foundation; with no
.\" Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
.\" Texts. A copy of the license is included in the `COPYING.DOC' file
.\" as part of this distribution.
.\" Format a function name with optional trailer: func_name()trailer
.de FN \" func_name [trailer]
.nh
.BR \\$1 ()\\$2
.hy
..
.\" Format a reference to section 3 of the manual: name(3)trailer
.de F3 \" func_name [trailer]
.nh
.BR \\$1 (3)\\$2
.hy
..
.\" Format the header of a list of definitons
.de DD \" name alt...
.ie "\\$2"" \{ \
.TP 8
.PD
.B \\$1 \}
.el \{ \
.PP
.B \\$1
.PD 0
.DD \\$2 \\$3 \}
..
.\" Start a code block: Note: groff defines an undocumented .SC for
.\" Bell Labs man legacy reasons.
.de SC
.fam C
.na
.nh
..
.\" End a code block
.de EC
.hy
.ad
.fam
..
.\" Format a structure pointer member: struct->member\fRtrailer
.de SPM \" struct member trailer
.nh
.ie "\\$3"" .IB \\$1 ->\: \\$2
.el .IB \\$1 ->\: \\$2\fR\\$3
.hy
..
.\" Format a function argument
.de ARG \" name trailer
.nh
.ie "\\$2"" .I \\$1
.el .IR \\$1 \\$2
.hy
..
.\" Hyphenation exceptions
.hw sarray carray lincom linterp
.\" gd_desync.3. The gd_desync man page.
.\"
.\" Copyright (C) 2012, 2014, 2016 D. V. Wiebe
.\"
.\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
.\"
.\" This file is part of the GetData project.
.\"
.\" Permission is granted to copy, distribute and/or modify this document
.\" under the terms of the GNU Free Documentation License, Version 1.2 or
.\" any later version published by the Free Software Foundation; with no
.\" Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
.\" Texts. A copy of the license is included in the `COPYING.DOC' file
.\" as part of this distribution.
.\"
.TH gd_desync 3 "25 December 2016" "Version 0.10.0" "GETDATA"
.SH NAME
gd_desync \(em check for a change of metadata on disk
.SH SYNOPSIS
.SC
.B #include <getdata.h>
.HP
.BI "int gd_desync(DIRFILE *" dirfile ", unsigned int " flags );
.EC
.SH DESCRIPTION
The
.FN gd_desync
function determines whether the metadata of the loaded
.ARG dirfile
has become desynchronised from the format specification fragments on disk, due
to a third party modifying the Dirfile metadata on disk after GetData opened
it. If
.ARG dirfile
has become desynchronised, this function can, optionally, reload the dirfile.
The
.ARG flags
argument influences how the function works. It should be zero or more of the
following flags, bitwise or'd together:
.DD GD_DESYNC_PATHCHECK
Ignore GetData's internal directory cache, and use the format fragments' full
path when checking for modifications. This flag is of particular importance
when the
.ARG dirfilename
passed to
.F3 gd_cbopen ,
or directory paths used in included fragments, contain symbolic links: with this
flag, these symbolic links will be re-evaluated. Without it, the target of
the symbolic links in effect when the dirfile was first opened will be
considered instead.
.DD GD_DESYNC_REOPEN
If this flag is specified, and
.FN gd_desync
detects desynchronisation, the Dirfile will be re-opened in place using the
exiting
.ARG dirfile
pointer. In this case, upon a positive result from this function, the caller
must discard all cached information about the dirfile, even the assumption that
.ARG dirfile
has been successfully opened.
Re-opening the dirfile is equivalent to calling
.F3 gd_discard ,
and then
.F3 gd_cbopen
with the same arguments used when originally creating
.ARG dirfile ,
except that the
.ARG dirfile
pointer doesn't change its value. As a result, this function may invoke the
registered parser callback function (see
.F3 gd_cbopen
and
.F3 gd_parser_callback ).
.SH RETURN VALUE
When successful, this function returns zero if the loaded dirfile has not
desynchronised, or one if it has. On error, a negative-valued error code is
returned, regardless of desynchronisation. Possible error codes are:
.DD GD_E_ALLOC
The library was unable to allocate memory.
.DD GD_E_BAD_DIRFILE
The supplied dirfile was invalid.
.DD GD_E_IO
An error occurred while trying to obtain the modification time of a fragment.
.PP
Additionally, if
.B GD_DESYNC_REOPEN
is used, this function may fail for any of the reasons listed in the
.F3 gd_discard
and
.F3 gd_cbopen
manual pages.
.PP
The error code is also stored in the
.B DIRFILE
object and may be retrieved after this function returns by calling
.F3 gd_error .
A descriptive error string for the error may be obtained by calling
.F3 gd_error_string .
.SH LIMITATIONS
The current implementation uses file modification times as reported by
.BR stat (2)
to detect changes. These times have a granularity of, at best, one second. As
a result, desynchronisation will not be detected in the case when a fragment is
modified, then GetData reads it, then the fragment is modified again, all within
one second. The caller may wish to perform its own monitoring using the
pathnames returned by
.F3 gd_fragmentname .
.PP
On systems lacking a POSIX.1-2008 conformant
.BR fstatat (2)
(q.v.), this function may always operate as if
.B GD_DESYNC_PATHCHECK
had been specified, regardless of the actual
.ARG flags .
.SH HISTORY
The function
.FN gd_desync
appeared in GetData-0.8.0.
In GetData-0.10.0, the error return from this function changed from -1 to a
negative-valued error code.
.SH SEE ALSO
.BR fstatat (2),
.BR stat (2),
.F3 gd_cbopen ,
.F3 gd_discard ,
.F3 gd_error ,
.F3 gd_error_string ,
.F3 gd_parser_callback
|