OpenSolaris

Printable Version Enter a New Search
Bug ID 6546230
Synopsis sharemgr: "nosuid=false" caused extra comma in share command's output
State 10-Fix Delivered (Fix available in build)
Category:Subcategory utility:filesystem
Keywords
Responsible Engineer Doug Mccallum
Reported Against snv_71
Duplicate Of
Introduced In solaris_nevada
Commit to Fix snv_76
Fixed In snv_76
Release Fixed solaris_nevada(snv_76) , solaris_10u6(s10u6_01) (Bug ID:2156348)
Related Bugs
Submit Date 16-April-2007
Last Update Date 29-April-2008
Description
See the following example:

# sharemgr add -s /export default
# sharemgr set -P nfs -p anon=0 -s /export default
# sharemgr set -P nfs -p nosuid=false -s /export default
# sharemgr show -p
default nfs=()
        /export  nfs=(anon="0" nosuid="false")
zfs nfs=()
# share 
-               /export   anon=0,   ""   <-- "anon=0" was followed by an extra comma

Note the trailing comma after "anon=0" in share command's output, it was caused because nosuid was set to "false" explicitly and share command("share" sub command of sharemgr, actually) couldn't generate proper output format in this case.

Ohter properties of boolean type(ie, nosub, etc.) have the same issue too.

BTW, the position of the extra comma is not always at the end of the attributes list in share command's output. Its position depends on where the value of nosuid property would be displayed if it was set to "true". For example, if we also ran the following command in the above example:

# sharemgr set -P nfs -S sys -p rw=client01 -s /export default

The output of share command was:

# share
-               /export   anon=0,,sec=sys,rw=client01   ""  

Note the two successive commas in the above output. I think that is a little confusing and should be fixed.
[dep, 17Sep2007]

  In addition to being able to cause this with different properties,
  setting more than one of those properties to false simultaneously can
  result in multiple superfluous commas.
Work Around
N/A
Comments
N/A