FreeCalypso > hg > freecalypso-tools
view rvinterf/include/ffslimits.h @ 407:19e5a3e2f9c0
fcup-settime: moved time() retrieval a little closer to the output
A fundamental problem with all simple time transfer tools is that there is
always some delay between the time retrieval on the source system and that
transmitted time being set on the destination, and the resulting time
on the destination system is off by that delay amount. This delay cannot
be fully eliminated when working in a simple environment like ours,
but we should make our best effort to minimize it. In the present case,
moving the atinterf_init() call before the time() retrieval should make
a teensy-tiny improvement.
| author | Mychaela Falconia <falcon@freecalypso.org> |
|---|---|
| date | Sat, 11 Aug 2018 21:52:17 +0000 |
| parents | e7502631a0f9 |
| children |
line wrap: on
line source
/* * Limits on FFS filenames and pathnames * * The deepest pathname allowed is one of the form /1/2/3/4/5/6, where the * last component may be a file, a directory or a symlink; if this last * component is a directory, it has to be empty, because any child of * that directory would violate the depth limit. * * The proper FFS pathname form begins with a slash (all pathnames must * be absolute, no Unix processes in the fw means no current directories), * has exactly one slash in each separating place (no double slashes), * and no trailing slash except in the special case of the root directory, * whose full pathname is "/". * * Each component name is [1,20] characters long; combining this limit * with the maximum depth of 6 puts the maximum length of a properly-formed * full pathname at 126 characters. */ #define MAX_FN_COMPONENT 20 #define MAX_NAME_DEPTH 6 #define MAX_FULL_PATHNAME ((MAX_FN_COMPONENT+1) * MAX_NAME_DEPTH)
