Jordan Brown (Sun) wrote: > Our application still has a couple of /etc/rcS.d scripts. > > Since they're legacy, we don't do anything explicit to register them > with SMF, and on uninstall don't do anything explicit to unregister them. > > After an uninstall, with the scripts deleted, we were surprised to see > that SMF still knew about them: > > $ svcs -v | grep scn > legacy_run - Feb_12 32 > lrc:/etc/rcS_d/S88SUNWscn-update-agent-prepare-singleuser > legacy_run - Feb_12 34 > lrc:/etc/rcS_d/S90SUNWscn-update-agent-singleuser > > $ ls /etc/rc*.d/*scn* > /etc/rc*.d/*scn*: No such file or directory If you didn't reboot, this is the expected behavior. At boot time, smf runs lsvcrun which start all legacy services. The lrc:/ services in the output of svcs just states that those services were started at boot time. SMF, however, has no knowledge of the current status of those services.
> > Does this situation cause any problems? I wouldn't expect any problem because of it. > How/when does SMF notice that we've installed a script? If it is a legacy service script (/etc/re*.d/*), at boot time. > Will SMF eventually realize that they are gone? When the system is rebooted. > Is there something we can or should do to prompt SMF to realize that > they are gone? As far as I know, just a reboot. -Antonello
