David Bustos writes: > Quoth Garrett D'Amore on Sun, May 13, 2007 at 09:40:41AM -0700: > > 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_. Obviously I've missed something here, but I feel lost > > in a maze of twisty passages that all say "SMF this way". :-( > > I haven't looked at your problem in-depth, but I can tell you that > those messages come from svc.startd being "proactive" about sending > commands to restarters. We encountered this when some kerberos service > changed its restarter from inetd to startd, IIRC. I believe that in the > past we have just release-noted that the messages are harmless. If you > want to avoid them completely, you have to remove the service from the > repository before boot.
Right. I had forgotten about this one. It's filed as 6368989. liane
