• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).


  • Subject: Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
  • From: 林 智子 <email@hidden>
  • Date: Wed, 29 Sep 2010 14:03:12 +0900

Dear Mike Mackovitch,
The wrong date problem does not occur with particular software.

The following log shows that the problem can be caused by a familiar
command zip:
----------------------------------------------------------------------
% /usr/bin/zip aaa.zip a
 adding: a (stored 0%)
% ls -luT aaa.zip
-rw-r--r--  1 emc01  student  152 Nov  9 02:25:14 1920 aaa.zip
----------------------------------------------------------------------
This result shows that zip command operation creates an archive having
wrong atime.

We hope this information will help you.

Sincerely,


On Tue, 28 Sep 2010 19:47:57 -0700
Mike Mackovitch <email@hidden> wrote:

> On Wed, Sep 29, 2010 at 09:17:39AM +0900, 林 智子 wrote:
> >
> > The captured data using tcpdump shows that the MacOSX client issued a
> > SETATTR call. However, the issued SETATTR call only specifies UID/GID.
> > The SETATTR call does not specify any timestamps that must be
> > specified by the NFS client.
>
> The SETATTR call does not specify any timestamps because the create
> call (the call into the NFS file system) did not specify any timestamps.
> The MacOSX NFS client has only ever set the attributes that were requested
> in the attributes passed in to the call.
>
> I'm sorry if you have some software that depends on these attributes
> to be set a particular way.  Unfortunately, nobody has requested this in
> the past and there is zero chance that we could fix the existing
> versions of MacOSX.  Therefore, unless your software will be requiring
> some future release of MacOSX in which the client may behave differently,
> you will need to solve this in your software.
>
> You were asking for a solution, so I mentioned a couple options.
>
> --macko
>


----
林 智子 <email@hidden>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >wrong atime created by NFS clients (Mac OX 10.5 and 10.6). (From: 林 智子 <email@hidden>)
 >Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6). (From: Mike Mackovitch <email@hidden>)
 >Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6). (From: 林 智子 <email@hidden>)
 >Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6). (From: Mike Mackovitch <email@hidden>)

  • Prev by Date: Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
  • Next by Date: How to execute an app with respect to the user in mac osx
  • Previous by thread: Re: wrong atime created by NFS clients (Mac OX 10.5 and 10.6).
  • Next by thread: FSGetCatalogInfo returns zero permissions for /Volumes/VolumeName directory
  • Index(es):
    • Date
    • Thread