Darren, thanks a lot!!!!

able to install the patch using the second method, adding an install 
account install:x:0:1:installpatch braindamage:/:/bin/true

of course, for security reasons, the account was deleted after the patch 
was installed.
not very comfortable with the idea of leaving an account with uid=0 even 
though it is a locked account.
I think Sun has to do something to fix this. Creating an account with 
uid=0 and leave it on the system is kind of risky. The auditors of my 
company will not buy it.
---------------------------------------------------------------------------------------------

Any comments or statements made in this transmission reflect the views of 
the sender and are not necessarily the views of the Federal Reserve Bank 
of New York.



Darren Dunham <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
10/28/2005 11:02 AM
Please respond to
Solaris-Users mailing list <[email protected]>


To
[email protected]
cc

Subject
Re: [Solaris-Users] KernelID and patch 112438-03







> /var/spool/patch/112438-03/SUNWcarx.u/install/checkinstall: 
> /var/spool/patch/112438-03/SUNWcarx.u/install/checkinstall: cannot open
> pkgadd: ERROR: checkinstall script did not complete successfully
> Dryrun complete.
> No changes were made to the system.
> #

Does the FAQ entry apply to your system?

http://www.science.uva.nl/pub/solaris/solaris2.html#q5.59
5.59) Patch installation often fails with "checkinstall" errors. 

When installing a patch, the Solaris 2.5+ patch installation procedure
will execute the script "checkinstall" with uid nobody.

If any of the patch files or if any part of the path leading up to the
patch directory cannot be read by nobody, an error similar to the
following will appear:


patchadd .                                               # or 
./installpatch .
Generating list of files to be patched...
Verifying sufficient filesystem capacity (exhaustive method) ...
Installing patch packages...
pkgadd: ERROR: checkinstall script did not complete successfully
....

You can workaround this in two ways, one is to make sure that the user
"nobody" can read all patch files and execute a "pwd" in the patch
directory or add an account "install" to /etc/passwd: 


                   install:x:0:1:installpatch braindamage:/:/bin/true

Installpatch and patchadd use "nobody" as a fallback if it cannot find
the "install" user. 

-- 
Darren Dunham                                           [EMAIL PROTECTED]
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >
_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users

_______________________________________________
Solaris-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/solaris-users

Reply via email to