On 14.06.09 09:20, Bernd Schemmer wrote:
Hi,
You'd write an SMF service (start method included) that does all the
configuration, then you'd pacakage it (with corresponding dependencies
on the pkgs that deliver the Oracl DB product), and you'd add this pkg
to the incorporation that your machines install.
Arrg - and that should be more secure than using a postinstall script???
Sorry, but using an SMF Service for configuring an application makes
developing of packages more complicated and will lead to lot of new
errors ....
And how could the postinstall start the database, if the install is not on the
live system? In case of live upgrade we have seen a lot of errors, where
packages were not trully relocatable. We also had packages
and patches which could not be deployed properly to a jumpstart image.
The package was checking for the architecture and as it was an x86
jumpstart server, it failed for a sparc package. Same if the package
expects hardware, which is available on the client, but not on the install server.
Best regards
Michael
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
