On Sun, Oct 13 2019, Philip Guenther <[email protected]> wrote: > ftp currently uses utime(3) to set the modification time on the retrieved > file. It set the access time on the file to the current time when doing > so. By converting this to use utimensat(), we can avoid the silly call > to time(3) to get the current time for the atime by instead passing > UTIME_NOW. > > However, I _think_ ftp does this just because utime(3) has no way to set > the modification time without also setting the access time and calling > stat(2) just to get the current atime (and dealing with the possible error > cases) wasn't worth it, so instead of setting the atime to the current > time with UTIME_NOW, I propose leaving the atime unchanged with > UTIME_OMIT. > > Thoughts? oks?
ok jca@ -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
