[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: utime
From: |
Jim Meyering |
Subject: |
Re: utime |
Date: |
Thu, 04 Mar 2010 16:03:10 +0100 |
Simon Josefsson wrote:
> Jim Meyering <address@hidden> writes:
>
>> Given that coreutils stopped using it then (no problems), and that
>> gnulib-tool has been warning anyone who uses it, outright removal
>> should be safe, now. Here's a patch to do that.
>> I'll push tomorrow if no one objects.
>
> Sounds good to me.
>
>> +On some old platforms (Sequent), @code{utime (file, NULL)} fails to set the
>> +file's timestamp to the current time.
>
> I'm assuming nobody cares about Sequent any more. If anyone does, it is
> in the git history.
>
>> On some platforms, this function mis-handles trailing slash:
>> Solaris 9.
>
> Is Solaris 9 considered too old as well? Or is this problem
> unimportant?
It's the function itself that is now irrelevant.
No one should be using utime anymore.
>From doc/posix-*/utime.texi:
@item
This function cannot set full timestamp resolution. Use
@code{utimensat(AT_FDCWD,file,times,0)}, or the gnulib module utimens,
instead.
- utime, Simon Josefsson, 2010/03/04
- Re: utime, Jim Meyering, 2010/03/04
- Re: utime, Simon Josefsson, 2010/03/04
- Re: utime,
Jim Meyering <=
- Re: utime, Eric Blake, 2010/03/04