[pfx] file system clock is 1 seconds ahead of local clock
Michael Orlitzky via Postfix-users <[email protected]>
| Newsgroups | gmane.mail.postfix.user |
|---|---|
| Message-ID | <aoWyj19U0TnjysIB@mertle> |
Every once in a while I see the warning in $Subject. The warning is raised in src/global/mail_stream.c, where I assume CAN_STAMP_BY_STREAM is false based on the following comment: /* * If we can cheaply set the file time stamp (no pathname lookup) do it * anyway, so that we can avoid whining later about file server/client * clock skew... * * XXX Unfortunately, Linux futimes() is not usable because it uses /proc. * This may not be available because of chroot, or because of access * restrictions after a process changes privileges. */ This is on a linux/glibc system, so I was curious about futimes(). The last mention of proc was removed from glibc's futimes() in 2014, when the mininum supported version of the linux kernel was bumped past 2.6.22: * https://repo.or.cz/glibc.git/commitdiff/cecf2ed43 * https://repo.or.cz/glibc.git/commitdiff/d0f5b3f85 According to its NEWS file, this was in glibc-2.24. Should HAS_FUTIMES now be defined on this platform, sparing me from figuring out what is going on with my clock? NB: grep suggests that HAS_FUTIMES_AT and HAS_FUTIMESAT do not agree on that underscore. _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]