On Thu, 17 Dec 2015, Ted Unangst wrote:
> Carsten Kunze wrote:
> > Ted Unangst wrote:
> >
> > > Probably not intended. Just an artifact left over from the era before you
> > > could set times on symlinks. (not likely that many people care, either.)
> >
> > I do care--I have a sync software (simi
Carsten Kunze wrote:
> Ted Unangst wrote:
>
> > Probably not intended. Just an artifact left over from the era before you
> > could set times on symlinks. (not likely that many people care, either.)
>
> I do care--I have a sync software (similar to rsync) which compares mtime and
> length. lst
Ted Unangst wrote:
> Probably not intended. Just an artifact left over from the era before you
> could set times on symlinks. (not likely that many people care, either.)
I do care--I have a sync software (similar to rsync) which compares mtime and
length. lstat needs do be done anyway so there
Carsten Kunze wrote:
> Hello,
>
> "cp -p" seems to not preserve the modification time of symlinks. This is not
> mentioned in the man page. Other systems I tested (others BSDs and Linux) do
> preserve the mtime of symlinks with e.g. "cp -a". The OpenBSD kernel also
> does support to set it w
Hello,
"cp -p" seems to not preserve the modification time of symlinks. This is not
mentioned in the man page. Other systems I tested (others BSDs and Linux) do
preserve the mtime of symlinks with e.g. "cp -a". The OpenBSD kernel also does
support to set it with e.g. utimensat(2).
Is this i
5 matches
Mail list logo