Quoth Vita Batrla on Tue, Nov 14, 2006 at 05:42:14PM +0100: > Hi, I try to make a patch, which upgrades a service on S10. The new > manifest is placed into /var/svc/manifest... and the service is upgraded > on next boot by manifest-import service. The old manifest file contains > element like the following example: > > <dependent > name='xyz' > grouping='optional_all' > restart_on='none'> > <service_fmri value='svc:/milestone/multi-user' /> > </dependent> > > The new manifest doesn't contain this dependency, so multi-user should > not directly depend on my service anymore. However, after the upgrade is > done on next boot, I check the properties or direct dependencies of > multi-user and the old dependency is still there. What is the correct > behaviour, should the upgrade remove dependency in multi-user, if the > new manifest deletes it or I have to run "special commands" to remove > the obsolete dependecy in multi-user manually?
The upgrade should automatically remove the dependency. Assuming you can reproduce this, please file a bug. David
