libshare may choose not to do it that way and leave it to the protocol
services to treat a share request as adding or replacing a share
based on whether or not the share already exists.
As I've responded to Pavel, sharefs is not doing anything with the
given data except passing it through to the protocol services.
Afshin
On 05/ 5/10 12:39 PM, Nicolas Williams wrote:
On Wed, May 05, 2010 at 12:30:05PM -0700, Afshin Salek wrote:
This might have been specified in libshare V2 design document but the
current behavior is unpublish followed by publish.
Couldn't that cause an outtage? If the re-share is just to change some
sharing option, there should be no hiccup for clients not affected by
the option change (e.g., security mode changes, where NFSv4 clients may
be able to recover automatically).
Nico
_______________________________________________
opensolaris-arc mailing list
[email protected]
