SMF does not always cleanup services that have been removed
The "svccfg cleanup" command and manifest-import script use different mechanisms to detect services without manifest files - svccfg uses the "manifestfiles" property group attached to each service, whereas the manifest-import script uses the SMF cache.
This means that the manifest-import command can on occasion fail to identify when cleanup needs to happen, and does not run the cleanup command. Running "svccfg cleanup" manually after boot is enough to clear up the problem.
The solution is to modify the manifest-import script so that it also refers to the "manifestfiles" property group.
Updated by Electric Monk about 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
commit 56bce6093e5a50ce1da04e68f5e22a53c35cc8a8 Author: Andrew Stormont <email@example.com> Date: 2017-02-06T23:11:06.000Z 7818 SMF does not always cleanup services that have been removed Reviewed by: Joshua M. Clulow <firstname.lastname@example.org> Approved by: Robert Mustacchi <email@example.com>