[pca] Kernel Patch 142909-17

[Diana Orrick]

  Thanks much!!

I believe this will be a helpful tool in the future.



On 10/11/2010 6:44 AM, Glenn Satchell wrote:
> patchadd spawns many sub-processes, so I get the PID of the pca 
> process, then run ptree frequently
>
> ptree 12345
>
> and look to see if the lowest level processes keep changing.
>
> % ptree 19993
> 459   /usr/lib/ssh/sshd
>   19911 /usr/lib/ssh/sshd
>     19912 /usr/lib/ssh/sshd
>       19922 -zsh
>         19984 /usr/bin/zsh -l
>           19993 perl -x -w /usr/local/bin/pca -i 143592
>             20023 sh -c /usr/sbin/patchadd 
> /tmp/pca.128679374919993/143592-05
>               20024 /usr/sbin/patchadd /tmp/pca.128679374919993/143592-05
>                 20026 /bin/ksh -hp /usr/lib/patch/patchadd -M 
> /tmp/pca.12867937
>                   20108 pkgadd -O patchPkgInstall -O nozones -O 
> enable-hollow-p
>                     20111 /usr/sadm/install/bin/pkginstall -O 
> patchPkgInstall -
>                       20112 /sbin/sh 
> /tmp/pca.128679374919993/143592-05/SUNWipf
>                         20113 cut -d- -f1
>
> regards,
> -glenn
>
> On 10/10/10 09:41, Diana Orrick wrote:
>> Thanks for the suggestions everyone, will supply more info when time
>> allows.
>> Still working on the cluster...
>>
>> On 10/9/2010 6:18 PM, Rajiv Gunja wrote:
>>>
>>> You might want to compare the times it took for other patches so that
>>> you know if it will take longer that 13*11*x minutes whet x is some
>>> random number which it seems to take for patching zones. If the server
>>> is ok to run for more time let it run. It took my server 7 hours to
>>> patch 200 patches on a server with 3 zones. Sine you have 13 zones it
>>> might take longer.
>>> -GGR
>>>
>>>> On Oct 9, 2010 12:17 PM, "Martin Paul" <martin at par.univie.ac.at
>>>> <mailto:martin at par.univie.ac.at>> wrote:
>>>>
>>>> Diana Orrick schrieb:
>>>>
>>>>
>>>> >
>>>> > Any suggestions on how to determine if the patching is progressing
>>>> at all?
>>>>
>>>> I guess you could use "truss -f -p <PID>" on the PID of the
>>>> "patchadd" process to see what's going on.
>>>>
>>>> If you have to interrupt the patch installation process, the only
>>>> "good" thing is that PCA is using plain patchadd for the patch
>>>> install, so there's no extra uncertainty added by the fact that you
>>>> are using PCA. On the other hand I don't have much practical
>>>> experience about how "patchadd" reacts to Ctrl-C. I think that it
>>>> should be pretty save to remove the partly installed patch with
>>>> "patchrm" afterwards without causing any ill effects.
>>>>
>>>> Martin.
>>>>
>>>>
>>
>

-- 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Diana Mayer Orrick, System Administrator
  Information Technology Services, Florida State University
        Contact:   orrick at fsu.edu   --   (850) 645-8009
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~