On (09/02/09 23:54), gm209912 wrote:
> Solution:
   :
> bash# ipadm set-prop -p privilege-ports=1048 tcp
> -- assign 1048 as privilege port
>
> bash# ipadm set-prop -p privilege-ports+=1049 tcp
> -- add 1049 as privilege port
>
> bash# ipadm set-prop -p privilege-ports-=1048 tcp
> -- remove 1048 as privilege port
>
> bash# ipadm show-prop -p privilege-ports tcp
> /* displays all the privilege ports */
>
> This model is also used by 'ppriv(1M)' to add/delete/assign privileges to 
> running process. I also remember Meem talking about this with regard to 
> en-mii.

the en-mii case was a bit different  because libdladm was trying to
form a set out of something that was being managed as discrete values
in the driver, with the full/half adding additional complexity, so that
keeping track of the current set required a lot of juggling of persistent
and current info (the latter was also hardwared dependant). priv-ports
is a bit simpler.

> Will the above model be helpful and nice thing to have in our framework?

the model is a good one, but I would suggest "extra-priv-ports"
since this is in addition to the default privileged-port range. 

--Sowmini

Reply via email to