Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Dec 2014 00:25:33 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 186293] tar(1): Problems with tar on FreeBSD 10.0
Message-ID:  <bug-186293-8-oO7CgK6BVS@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-186293-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-186293-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186293

Rick Macklem <rmacklem@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rmacklem@FreeBSD.org
           Assignee|freebsd-bugs@FreeBSD.org    |rmacklem@FreeBSD.org
             Status|In Progress                 |Open

--- Comment #9 from Rick Macklem <rmacklem@FreeBSD.org> ---
I will work on a mount option that forces the client to
set the times to the server's value as a work around
for this.

I'll leave this open until the mount option has been
implemented.

Fyi, the NFSv3 protocol (RFC-1813) does not provide any
way to set an ACL. (That is a Solaris unpublished protocol,
unless you are using NFSv4.)
Also, there is nothing in RFC-1813 that suggests that
only one attribute can be set in a Setattr RPC.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-186293-8-oO7CgK6BVS>