Danek Duvall wrote: > If the file is just a file -- not an editable (preserve=true) file -- then > it'll just be updated. Otherwise, it'll be updated as long as it hasn't > been changed. > If it has been changed, then it gets left alone. In order to force changes
It is listed in SUNWcsr as: e pkcs11confbase etc/crypto/pkcs11.conf 644 root sys So I guess that means it is editable and doesnt meet the criteria above. My putback is updating pkcs11confbase to include the new provider by default on new installations. My interpretation of the above statement is that the file will still be updated if the existing file on the system was not modified. > into it, you need to deliver the fragments you wish to add to the file into > some known (but possibly private) location, and have some software run > prior to it being used that can merge those fragments. If there's already > some piece of software that always runs before the file is used, then it > can be modified to do the merge. Otherwise, you can deliver an SMF service > that will do it for you (an existing one may do the trick, too), and mark > the file with the tag "restart_fmri=...". > > See Casper's putback recently to do this for the RBAC files. I see Casper's bug report (6851603) and have looked at his fixes but I don't think I can leverage what he already did for this case. Are there other examples of a file that uses "restart_fmri"? I searched the ONNV tree and did not locate any. -Wyllys _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
