Solaris Package packaging and class scripts

Solaris Package packaging and class scripts

Post by haydud » Thu, 05 Oct 2006 19:09:05

Hi All,

I was wondering if anyone had experience with Solaris packaging. I am
having troubles with scripts failing when the package is installed, but
running fine when unit tested.

For example, I want a new service (Solaris 10) imported when the
package is installed:

in my Prototype I have:

i in.manifest <--- the script to run at install time that imports the
f manifest myservice.xml

in.manifest has the instructions to copy myservice.xml in its place
(this part works) and to import the service with:

[full path to]/svccfg import [full path to]/myservice.xml.

When I run this from my shell it works. When this is run through a
"pkgadd" instead, svccfg fails with error 255.

May anyone have a clue on what I am missing?


Solaris Package packaging and class scripts

Post by Chris Rid » Fri, 06 Oct 2006 04:21:41

On 2006-10-04 11:09:05 +0100, "haydude" < XXXX@XXXXX.COM > said:

The Blastwave folks describe what they do at
< ;. It is definitely worth a
read and/or cut & paste :-)

The only thing we do differently from them is to not enable the service
in the postinstall, as our stuff needs non-trivial configuration first.