Re: [pca] different directory for patches
Was there a solution to this problem ? We are considering the use of this tool in our Environment but we do have linked directories for /var/sadm/pkg on some of our servers. Thanks, Brad CSC Unix Adminstrator From: pca-boun...@lists.univie.ac.at [mailto:pca-boun...@lists.univie.ac.at] On Behalf Of McGranahan, Jamen Sent: Wednesday, January 16, 2013 12:38 PM To: PCA (Patch Check Advanced) Discussion (pca@lists.univie.ac.at) Subject: [pca] different directory for patches Is there a way I can force patchadd to look in a different directory than the default /var/sadm/pkg directory? We created a softlink from /var/sadm/pkg to /apps/sadm/pkg (due to space issues), but now patchadd always fails: Directory is expected, found link - /var/sadm/pkg. Failed (exit code 1) Showrev -p does fine; and downloading the patches with pca -d does fine as well. It's just the actual installation of the patches where it fails. I'm pretty sure I had this fixed before, but honestly, I don't remember what I did (plan to DOCUMENT what I do this time!). Any ideas/suggestions would be greatly appreciated! Thanks! Jamen McGranahan Systems Services Librarian Vanderbilt University LIbrary Central Library Room 811 419 21st Avenue South Nashville, TN 37214
Re: [pca] different directory for patches
Am 23.01.2013 15:06, schrieb Stevenson, Bradley (NE): Was there a solution to this problem ? We are considering the use of this tool in our Environment but we do have linked directories for /var/sadm/pkg on some of our servers. The solution is to *not* use a symbolic link for /var/sadm/pkg/. That's an issue with Suns/Oracles patch tools (like patchadd), BTW, and not PCA. As Dagobert mentioned, use a loopback mount instead: rm /var/sadm/pkg mkdir /var/sadm/pkg mount -F lofs /apps/sadm/pkg /var/sadm/pkg You can also make this permanent via vfstab. hth, Martin.
Re: [pca] different directory for patches
Am 23.01.2013 15:30, schrieb Stevenson, Bradley (NE): What if its /var/sadm that is linked. Would using the loopback Method work in this case as well ? Yes, it's highly recommended. Google for /var/sadm symbolic link for more examples of this recommendation. hth, Martin.
Re: [pca] different directory for patches
What if its /var/sadm that is linked. Would using the loopback Method work in this case as well ? -Original Message- From: pca-boun...@lists.univie.ac.at [mailto:pca-boun...@lists.univie.ac.at] On Behalf Of Martin Paul Sent: Wednesday, January 23, 2013 8:20 AM To: PCA (Patch Check Advanced) Discussion Subject: Re: [pca] different directory for patches Am 23.01.2013 15:06, schrieb Stevenson, Bradley (NE): Was there a solution to this problem ? We are considering the use of this tool in our Environment but we do have linked directories for /var/sadm/pkg on some of our servers. The solution is to *not* use a symbolic link for /var/sadm/pkg/. That's an issue with Suns/Oracles patch tools (like patchadd), BTW, and not PCA. As Dagobert mentioned, use a loopback mount instead: rm /var/sadm/pkg mkdir /var/sadm/pkg mount -F lofs /apps/sadm/pkg /var/sadm/pkg You can also make this permanent via vfstab. hth, Martin.
Re: [pca] different directory for patches
Great! Does anyone know if the script will do disk space checking so it knows How much disk space it needs to install the patches. Or does anyone have a Script to do this ? Brad -Original Message- From: pca-boun...@lists.univie.ac.at [mailto:pca-boun...@lists.univie.ac.at] On Behalf Of Brookins, Neil (Philadelphia) Sent: Wednesday, January 23, 2013 9:30 AM To: 'pca@lists.univie.ac.at' Subject: Re: [pca] different directory for patches Last week, after reading Dagobert's email about the loopback, I tested it on one of my servers which had a sym link for /var/sadm and it worked beautifully. I was able to reboot and it mounted the loopback correctly from the vfstab entry too. Now I'm able to install new patches without the sym link getting removed. What had been happening (with the sym link) is that some patch installs worked ok, others would blow away the sym link. Then the next patch attempt would fail because it thought the dependency was missing because the list of existing patches was no longer accessible. Neil Brookins - Original Message - From: Stevenson, Bradley (NE) [mailto:bradley.steven...@gd-ais.com] Sent: Wednesday, January 23, 2013 09:30 AM To: PCA (Patch Check Advanced) Discussion pca@lists.univie.ac.at Subject: Re: [pca] different directory for patches What if its /var/sadm that is linked. Would using the loopback Method work in this case as well ? -Original Message- From: pca-boun...@lists.univie.ac.at [mailto:pca-boun...@lists.univie.ac.at] On Behalf Of Martin Paul Sent: Wednesday, January 23, 2013 8:20 AM To: PCA (Patch Check Advanced) Discussion Subject: Re: [pca] different directory for patches Am 23.01.2013 15:06, schrieb Stevenson, Bradley (NE): Was there a solution to this problem ? We are considering the use of this tool in our Environment but we do have linked directories for /var/sadm/pkg on some of our servers. The solution is to *not* use a symbolic link for /var/sadm/pkg/. That's an issue with Suns/Oracles patch tools (like patchadd), BTW, and not PCA. As Dagobert mentioned, use a loopback mount instead: rm /var/sadm/pkg mkdir /var/sadm/pkg mount -F lofs /apps/sadm/pkg /var/sadm/pkg You can also make this permanent via vfstab. hth, Martin. Notice of Confidentiality This transmission contains information that may be confidential. It has been prepared for the sole and exclusive use of the intended recipient and on the basis agreed with that person. If you are not the intended recipient of the message (or authorized to receive it for the intended recipient), you should notify us immediately; you should delete it from your system and may not disclose its contents to anyone else. This e-mail has come to you from Towers Watson Delaware Inc.
