On 04/22/10 12:17, Hai-May Chao wrote:
I have some questions relating to IPS....
I'd like to have a package, for example pkg:/ABC (a new or an existing
package)
which needs to depend on a NSS package (pkg:/system/library/mozilla-nss)
with
"require" type dependency.
That's simple enough.
I'll have a new SMF service in pkg:/ABC which will access a database
library in
the NSS package to extract certificates and store them in the system. I
need to
re-generate these certificates when the database is updated via a
reinstall or
upgrade of the NSS package.
Can a connection be made between these two packages in IPS such that this
new SMF service in one package can be restarted when the external package
gets updated? Any suggestions?
There's no way right now to do this easily.
Or must this new service be in the NSS package itself? This relates to
my other
question - How is the NSS package being delivered as
system/library/mozilla-nss?
We don't own its source and it is not in ON. Any pointers would be
appreciated.
From an interface standpoint, you have a dependency on the
value of the certs delivered by the NSS package. hmmm.. more on
that in a bit...
First of all, your service should always check at startup whether the
relevant file has been modified since you extracted the certs; if, so
it should redo the initial extraction.
You could add a restart_fmri tag to the cert file in the NSS package for
your service; it would then get started on a live system if that file
were updated. If your service is transient, then this is really your
only option.
But... why are you extracting these certs from the NSS package? What
other meanings are you attaching to them? Is run-time extraction really
the correct answer?
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
