From 7acad7856885dd41270a047a336ad1e7ff6cb4c0 Mon Sep 17 00:00:00 2001 From: "A. Wilcox" Date: Wed, 11 Apr 2018 23:43:19 -0500 Subject: pathconf: add _PC_TIMESTAMP_RESOLUTION Right now, this is a worst-case assumption; some kernels may actually have a value of 100000 here (100 Hz timers). This is considered the easiest implementation. This is required to be present in . --- src/conf/fpathconf.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'src') diff --git a/src/conf/fpathconf.c b/src/conf/fpathconf.c index e6aca5cf..b6a9d63e 100644 --- a/src/conf/fpathconf.c +++ b/src/conf/fpathconf.c @@ -4,7 +4,7 @@ long fpathconf(int fd, int name) { - static const short values[] = { + static const long values[] = { [_PC_LINK_MAX] = _POSIX_LINK_MAX, [_PC_MAX_CANON] = _POSIX_MAX_CANON, [_PC_MAX_INPUT] = _POSIX_MAX_INPUT, @@ -25,7 +25,8 @@ long fpathconf(int fd, int name) [_PC_REC_XFER_ALIGN] = 4096, [_PC_ALLOC_SIZE_MIN] = 4096, [_PC_SYMLINK_MAX] = -1, - [_PC_2_SYMLINKS] = 1 + [_PC_2_SYMLINKS] = 1, + [_PC_TIMESTAMP_RESOLUTION] = 100000000, }; if (name >= sizeof(values)/sizeof(values[0])) { errno = EINVAL; -- cgit v1.2.3-70-g09d2