Menno Lageman wrote: > Dropping the "Extended" prefix may lead to confusion with the 'classic' > accounting described in acct(1M). And the subsystem managed by > acctadm(1M) is called Extended Accounting, so having that in the name > seems the logical thing to do.
I actually think it is the opposite. The command isn't extendedacctadm or eacctadm it is just acctadm. I think the Extended prefix is useless in the RBAC profile name and only adds to the confusion already created by having both acct(1M) and acctadm(1M) referring to different generations of the subsystem. In RBAC profile naming we already have precedence for multiple 'generations' being covered by a single profile. Consider the 'Name Services Security' profile it covers commands used in NIS, NIS+ and LDAP. > The SMF FMRI does not contain the word "accounting" for the same reason. > I entertained the thought of using "extended accounting" in the FMRI but > decided that was too long to be useful. Instead, I followed the > convention used for the FMRI for coreadm(1M). Now that you mention it I think that it should be called accounting in the FMRI. The practice of naming the FMRI after the current CLI implementation used to control it isn't so good in my opinion, the FMRI should describe the service not the admin interface command, eg it is network/ssh not network/sshd and network/system-log not network/syslogd. -- Darren J Moffat
