On 4/7/20 4:19 PM, Thomas Gleixner wrote: > "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx> writes: >> I've tried to capture this info, as well some other relevant errors >> in the following text. Does it look okay? >> >> Writes to the timens_offsets file can fail with the following >> errors: >> >> EINVAL An offset-nanosecs value is greater than 999,999,999. >> >> EINVAL A clock-id value is not valid. >> >> EPERM The caller does not have the the CAP_SYS_TIME capability. >> >> ERANGE An offset-secs value is out of range. In particular; >> >> · offset-secs can't be set to a value which would make the >> current time on the corresponding clock inside the names‐ >> pace a negative value; and >> >> · offset-secs can't be set to a value such that the time on >> the corresponding clock inside the namespace would exceed >> half of the value of the kernel constant KTIME_SEC_MAX >> (this limits the clock value to a maximum of approxi‐ >> mately 146 years). > > Yes. Thanks! Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
