SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
01-05-2008, 11:52 AM
| ||||
| ||||
 InstallP permissions problem Hi I have a simple test.bff which puts a file dummy inside /opt/some_dir/ dummy. I run this command using installp -d . test.cmp. The files gets copied appropriately but the directory permissions of /opt becomes drwxr-x--- whereas it has to be drwxr-xr-x ( the permissions that was before installp was run ). Any ideas ? -Karthik      |
|
01-05-2008, 11:52 AM
| |||
| |||
| Re: InstallP permissions problem On Aug 20, 5:43 pm, Karthik <karthik3...@gmail.com> wrote: > Hi > > I have a simple test.bff which puts a file dummy inside /opt/some_dir/ > dummy. I run this command using > installp -d . test.cmp. The files gets copied appropriately but the > directory permissions of /opt becomes drwxr-x--- whereas it has to be > drwxr-xr-x ( the permissions that was before installp was run ). Any > ideas ? > > -Karthik Depending on your build system remove ./opt from the package list or set the the correct permissions on the ./opt ( NOT /opt ) and read http://publibn.boulder.ibm.com/doc_l...w4_install.htm man mkinstallp view /usr/lpp/bos/README.MKINSTALLP ( Note 4 ) search this group for mkinstallp hth Hajo |
|
01-05-2008, 11:52 AM
| |||
| |||
| Re: InstallP permissions problem Hajo Ehlers wrote: > On Aug 20, 5:43 pm, Karthik <karthik3...@gmail.com> wrote: > >>Hi >> >>I have a simple test.bff which puts a file dummy inside /opt/some_dir/ >>dummy. I run this command using >>installp -d . test.cmp. The files gets copied appropriately but the >>directory permissions of /opt becomes drwxr-x--- whereas it has to be >>drwxr-xr-x ( the permissions that was before installp was run ). Any >>ideas ? >> >>-Karthik > > > > Depending on your build system remove ./opt from the package list or > set the the correct permissions on the ./opt ( NOT /opt ) and read > > http://publibn.boulder.ibm.com/doc_l...w4_install.htm > > man mkinstallp > > view /usr/lpp/bos/README.MKINSTALLP ( Note 4 ) > > search this group for mkinstallp > > hth > Hajo > Make sure there is not an entry for /opt in the FILESET.inventory file within the liblpp.a archive. You should probably double check the FILESET.al file in the liblpp.a also. Paul Landay |
|
01-05-2008, 11:52 AM
| |||
| |||
| Re: InstallP permissions problem > From: "Karthik Krishnamurthy" > To: "Paul Landay" > Date: Tue, August 21, 2007, 12:32:00 > Subject: Re: InstallP permissions problem > >> Make sure there is not an entry for /opt in the FILESET.inventory >> file within the liblpp.a archive. You should probably double >> check the FILESET.al file in the liblpp.a also. > > If Iam not wrong, the directory or file permissions should be retained > in the install machine right ? How is it getting modified. ? If multiple installp image have a reference to the same file/directory in their respective FILESET.inventory or FILESET.al members then which ever installp image is installed last 'wins'; at least as far as permission bits and owner/group are concerned. The 'lslpp -w FILENAME' or 'lslpp -w DIRNAME' command will show you which fileset(s) currently claims ownership of that file or directory. On my AIX 5.3 system it shows: # lslpp -w /opt File Fileset Type ----------------- ---------------- --------- /opt bos.rte Directory so the /opt directory is 'owned' by the bos.rte fileset. When debugging your home-grown installp images, try this: export INST_DEBUG=yes installp ... then you will see all the steps that installp goes through. Paul Landay |
|
01-05-2008, 11:52 AM
| ||||
| ||||
| Re: InstallP permissions problem On Aug 20, 8:43 am, Karthik <karthik3...@gmail.com> wrote: > Hi > > I have a simple test.bff which puts a file dummy inside /opt/some_dir/ > dummy. I run this command using > installp -d . test.cmp. The files gets copied appropriately but the > directory permissions of /opt becomes drwxr-x--- whereas it has to be > drwxr-xr-x ( the permissions that was before installp was run ). Any > ideas ? > > -Karthik I had a similar issue as well and was able to fix it. In my package build environment I have a directory source tree, which starts with root/opt/..... My installation package sets the permissions based on the permissions set in that source tree. In my environment, the opt directory was set differently than on the system, and during the install process, my installation package was changing the system opt to the security setting from my source tree. Once I changed mine to match the system and rebuilt the install package, the problem went away. Cheers, BBM |
Linear Mode
