Garrett D'Amore wrote: > As part of PSARC 2002/356, I've got an RFE to eradicate in.tnamed > (death to IEN-116!). > > I've put together a webrev for my changes so far, at > http://cr.grommit.com/~gdamore/tnamed/webrev/ > > However, it was pointed out to me that my attempt to just remove the > XML file for the tnamed service is probably not adequate in the fact > of system upgrades or BFU. Apparently some magic may be required to > make SMF aware of it. > > I'm almost completely ignorant of SMF, so I would really like some > advice about how best to achieve this so that I can finally put > IEN-116 to rest. If any one has a simple recipe, or can send me a > webrev for a similar case, I'd love to see it. > > /me now wishes he had removed in.tnamed back in 2002, before he > departed Sun, and before it got "SMFified". > Garrett,
It's not adequate to just remove the service manifest and binaries since the service is still registered in the repository. We need to explicitly svccfg delete the service. Ideally, the r.manifest script in the package delivering the service would accomplish this but unfortunately that's not the case due to *6438829 SMF svcs are not removed when performing a pkgrm in an alternate root <http://monaco.sfbay/detail.jsp?cr=6438829>* The following discussion http://www.opensolaris.org/jive/thread.jspa?messageID=73038 details the problem and suggests two workarounds that you can use. Hope that helps, -tony
