Originally posted by: SystemAdmin

I have a package that stops and starts a process in the preinstall and postinstall scripts respectively. Now after installing this package on the base OS and then creating a wpar ( just use mkwpar and donot issue startwpar ) I see that the install scripts are re-run on the base OS. Is it expected ?

The problem with this being, my process on the base OS is restarted but the configuration parameters of that process are placed under /wpars/<wpar name>/var/opt/<package name>/ instead of /var/opt/<package name>. This causes my process not performing the way it is supposed to. The PPID of the process is shown as "1", but it is configured as if it is running in a wpar. I dont even issue "startwpar <wpar name" but still see this issue.

Can someone please help me out with this.

Thanks,
-Pavan.

Originally posted by: drajarsh

Initially the package got installed in the global environment. Subsequently after you created a system WPAR (via mkwpar), the package got installed again: this time in the WPAR, which is why you notice that the configuration is available within /wpars/<wparname>/...

Are you installing application software or OS software?

Are you using defaults while doing a mkwpar? Defaults would mean you have a shared /usr and /opt. Because if you are using defaults, it is recommended to install the OS software in a global env (the LPAR) and then sync your newly created WPAR (not reinstall in WPAR).

On the other hand, if you are using private /usr and /opt, you would need to install the OS software in the LPAR first and then again reinstall in your WPAR.

For application software you need to install it only in the WPAR.

Each WPAR has its own init process which is the PPID ('1') you see for your process within the WPAR.

Originally posted by: SystemAdmin

Thanks for the inputs. Nevertheless, I got around with the problem by guarding my statements with INUCLIENTS.