If the supporting manifests have been removed for the services then the services will be removed.
Although, there is a problem where the graph engine is started and already recognizes these services, which have a restarter other than startd. Therefore the graph engine queues the start for the alternate restarter and then queues the deletion. When inetd (the alternate restarter in this case) starts and the queued events are processed the starts occur before the deltions, there for inetd complains. This complaint should only be on the first reboot after upgrade. The Early Manifest Import project improve over this issue, as services will be recognized for removal before the graph engine starts. On Nov 16, 2009, at 2:11 PM, Alan Coopersmith wrote: > Bill Shannon wrote: >> I just upgrade from snv_111 to snv_127 and ran into a few issues: >> >> 1. When booting I got a bunch of complaints from inetd of the form >> "Failed to update state of instance" and "Failed to get instance for" >> referencing svc:/application/x11/xfs (I think). And indeed I have >> no such service. Is this a bug? Is something misconfigured on my >> system? > > The xfs (X Font Server) SMF service manifest was previously installed > whenever X was installed, even when the xfs service wasn't, so trying > to connect to it would generate errors. It was moved to the package > containing the xfs server, which isn't installed by default and which > few people add, since they're not trying to serve old-fashioned X > terminals or other similar remote environments without local fonts. > > On upgrade, SMF now sees the service manifiest is removed but somehow > seems to not be cleaning up properly. > > -- > -Alan Coopersmith- alan.coopersmith at sun.com > Sun Microsystems, Inc. - X Window System Engineering > > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org >
