On Mon, Mar 25, 2013 at 06:23:06PM +0100, Richard PALO wrote: > Le 25/03/13 17:16, Marcel Telka a écrit : > >>So if I translate, you mean that when nosuid is on the server, any > >>setuid or device operation will 'silently' fail, and in any case, > >>the child doesn't know beforehand. > > > >No "setuid or device operation", but chmod(2) operations trying to set setuid > >or setgid bits will have no effect. IOW, you'll not be able to do something > >like > >"chmod u+s file" or "chmod g+s file". It will just do nothing. > > > I understand. But just to understand my question consider swapping > suid/nosuid for rw/ro. > > In this case, if sharenfs is 'ro' for a given client, what does > mount show (and allow) "ro" or "rw"?
share options are in general not related to, nor negotiated with the client. So in your example you could mount rw, even the share is ro. You'll just get EROFS when attempting to write. -- +-------------------------------------------+ | Marcel Telka e-mail: [email protected] | | homepage: http://telka.sk/ | | jabber: [email protected] | +-------------------------------------------+ ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
