topic Re: custom patch manager make_depot problem in Operating System - HP-UX

custom patch manager make_depot problem

John Henrikson — Tue, 08 Jul 2003 15:39:27 GMT

Hi-
I'm having a problem when I try to use the make_depot script that comes with my custom patch bundle.. I download all the patches ok, but when it goes to decompress the patches it tries to do it in the /tmp directory and I don't have enough space there for some of the patches to be expanded, so it fails. I have plenty of room for the patches in the destination depot directory..
Any advice would be appreciated.. thanks!!

Re: custom patch manager make_depot problem

Steven E. Protter — Tue, 08 Jul 2003 15:43:37 GMT

Try it in another directory, you don't have to use /tmp

There are probably processes with open files that haven't terminated yet, even though the files themselves are gone.

/tmp is a suggestion for creating the depot, not a requirement.

SEP

Re: custom patch manager make_depot problem

John Henrikson — Tue, 08 Jul 2003 15:45:52 GMT

Thanks, but I guess I wasn't clear enough in the original post.. I am using another directory.. /data3/depot and running the ./make_depot script from there.. but the script itself uncompresses the files in /tmp..
hence I suppose I could go into the script and try to change every occurance of /tmp to something else.. just wondered if there were an easier way..
thanks.

Re: custom patch manager make_depot problem

James R. Ferguson — Tue, 08 Jul 2003 15:51:31 GMT

Hi John:

Part of the problem is that unpacking the shell archive uses 'here' documents which create temporary files in '/tmp'. The location of these temporary files is not user-managable.

If this is an 11.0 system, this behavior was changed with patch PHCO_20816 (where PHCO_27344 is the lastest superceding patch).

With this patch, Posix shell 'here' documents are deposited in '/var/tmp' instead of the usually smaller 'tmp'.

If this is 11.11, this should be inherent.

Regards!

...JRF...

Re: custom patch manager make_depot problem

Robert Salter — Tue, 08 Jul 2003 15:53:45 GMT

John,

Steve's right, you're not locked in to using /tmp. The README file with the bundle informs you that the make_depot will need 2-3 times more space than the size of the patches.

Just did the same thing this past weekend, find a place on your server that has some room, the depot file I ran was 220mb for only 70 patches. I created a directory named patches in a file system with extra space and copied the xxxx.sh file there, did the sh on it and ran make_depot, badda boom! badda bing! It's such a sweet thing.

Re: custom patch manager make_depot problem

John Henrikson — Tue, 08 Jul 2003 17:01:55 GMT

Well the system does have PHCO_20816 installed and the patches still want to be decompressed in /tmp, no matter where I run ./get_patches from..
Is my only option then to make the depot manually?

thanks
John H.

Re: custom patch manager make_depot problem

Christopher McCray_1 — Tue, 08 Jul 2003 17:18:34 GMT

Hello,

That is one of the disadvantages of using cpm. You will need a /tmp of at least 512Mb and that is if you install frequently. It asks you during the download and again during the creation process if your have XXX space in /tmp. You should try to modify your script to make it go to another directory, or increase /tmp at the next available time.

Sorry,
Chris

Re: custom patch manager make_depot problem

Pete Randall — Tue, 08 Jul 2003 17:20:41 GMT

It seems to me that I remember someone modifying the get_patches script. Can you edit it?

Pete

Re: custom patch manager make_depot problem

John Henrikson — Tue, 08 Jul 2003 17:28:33 GMT

It never askes me if I have space in /tmp, just in the directory I'm running make_depot from..
nevertheless I appreciate your help.. I've changed the script and will see if that will work..

John H.

Re: custom patch manager make_depot problem

Richard Ace_1 — Wed, 09 Jul 2003 14:31:01 GMT

This is what I do when I install software .

It may help

See Attached

Cheers

Rich