"Garrett D'Amore" writes: > Liane Praza wrote: > > Liane Praza writes: > > > >> Sorry Garrett, for not seeing this sooner. > >> > >> "Garrett D'Amore" writes: > >> > >>> I'm trying to debug a problem with SMF & inetd as part of the removal > >>> of in.tnamed. Basically, I can't seem to figure out why inetd still > >>> spews this message on the first reboot after an upgrade: > >>> > >>> /var/adm/messages.0:May 12 22:45:11 surya-x4200 inetd[28174]: [ID 702911 > >>> daemon.error] Failed to update state of instance > >>> svc:/network/tname:default in repository: entity not found > >>> /var/adm/messages.0:May 12 22:45:11 surya-x4200 inetd[28174]: [ID 702911 > >>> daemon.error] Failed to update state of instance > >>> svc:/network/tname:default in repository: No such file or directory > >>> > >>> What I can't tell, is why inetd even knows about network/tname. It > >>> should be _gone_. > >>> > >> > >>> I've posted a webrev of what I've figured out so far: > >>> > >>> http://cr.grommit.com/~gdamore/6656092/webrev/ > >>> > >> I'm perplexed as well. The code in postinstall should have done it. > >>
> >> To clarify, the message only appears during the first boot after upgrade, > >> not a subsequent one? > > Correct. I'm wondering if there is some cruft left behind in an SMF > database somewhere that svccfg delete isn't actually deleting. But then it wouldn't go away after the reboot. > > For the record, I've been directed to submit an RTI, but I need two > reviewers for these changes. Does your review count at least as one of > them? It certainly will resolve the "hang on upgrade" part of the problem, and I'm OK with it going back to resolve that. We do need to resolve the messages on first reboot bit too, but that can be done post-64 respin. liane
