Some of you may recall my recent putback of the removal of in.tnamed.
Well, there has been some nasty fallout, thanks to SMF and the upgrade process. snv64 (which will have to be respun as a result of this nastiness) was hanging during upgrade, thanks to chicken and egg dependencies in the upgrade script.
I fixed the hang, but there is a warning message coming from inetd that I can't seem to locate.
Along the way, I've found references to the network/tname service in a few surprising places. The things I've had to edit, thanks to SMF:
And *still* we see a warning from inetd. See 6556092 in bugster for more info.
Anyway, I'm waiting for folks to decide whether to allow the warning to stay, or to backout the change to remove in.tnamed. If the later is taken, I will run screaming from the process, and just leave in.tnamed alone.
In my opinion, removing the tname.xml should have been sufficient. But thanks to SMF's binary databases, it creates a major headache. Can someone from the SMF team please unravel this maze?
posted by Garrett D'Amore at 9:57 AM on May 13, 2007
"Learning to hate SMF"
No comments yet. -