Just FYI - it seems as if updates to the patchdiag.xref have been
suspended once again. The most recent file I get is:
## PATCHDIAG TOOL CROSS-REFERENCE FILE AS OF Mar/20/09 ##
Martin.
Norman Lyon wrote:
I see what you see in S9 and S10. I don't care about S8, but the story
is a tad more complex with more than just 2 architectures (sun4[dmu]).
Yes. And for me, who'd be interested in a fool-proof solution for all
Solaris versions it's getting too complex I guess. One thing
Norman Lyon wrote:
Wait Can't we just drop the '.$ARCH' concern and look at the REV=
part of the VERSION? From my initial checking, I'm seeing that the
multiple package names are showing up with different versions...
Seems as if we're getting to the very core of the problem. You are
Hi Norman,
To begin with - I'm far from being a Sun patch guru, I'm still learning
something new from time to time :) Maybe Don O'Malley can add something
to the subject as well.
I've run into problems where a patch may need to be re-installed if
someone has added a package after patching.
Norman Lyon wrote:
My solution to the $PKG.$ARCH issue has been to cutoff the trailing
architecture letters, if they match my particular architecture, along
the lines of the following (please forgive the sloppiness, since this is
quick and dirty, and doesn't look at the patchdiag.xref yet).
Jeff,
Thanks for the info Martin. Just so I make sure I have it straight, if I
specify a specific patch to install, not a specific revision of a patch,
then PCA assumes I know the package dependencies and will take action to
resolve any other patch dependencies, correct?
Right. pca -i 123456
Simon,
I had hoped someone else would follow up, as my practical experience
with zones (and patching them) is close to zero.
I patch the global zone and allow pca to patch the non-global zone as
well.
When I query any missing patches in the non-global zone it reports many
but when I try to
Alexander,
--16:22:21-- http://winds06.win.ch.da.rtr/cgi-bin/pca-proxy.cgi?119252-28
= `/data/patches/winds06/119252-28.tmp'
Resolving winds06.win.ch.da.rtr... 10.0.1.26, 10.0.1.26
Connecting to winds06.win.ch.da.rtr|10.0.1.26|:80... connected.
HTTP request sent, awaiting
Gehring, Andrew wrote:
I have two systems, that are identical in both hardware and software
(Solaris 10 8/07 s10s_u4wos_12b SPARC).
Ok, that's a good start. As Don mentioned, it can get complicated with
pre-installed patches if you try to do that with different update releases.
Patches
Hi Don,
We have identified a new problem occurring on some of the download servers
sitting behind the load balancer, whereby requests to download patches which
require a support contract from some of the download servers are intermittently
producing a HTTP 403 Error.
Ok, so this explains
All things are opened to debate.
Sure. pca wouldn't be what it is without the enormous amount of user
feedback.
I just wanted a little more logging. Not exactly what was in sunucLog.
Can you give an example of what you would like to see in the logs? I
just can't think of anything
Jan Holzhueter wrote:
Just run into the same problem. But for me I just can't get old patches
like 118825-01. But I can't get them form the webpage either :(
I can download never Patches though e.g. 140781-01
Yes, something's broken. I get 403 Forbidden for e.g. both these:
118825 -- 02 ---
benjamin_d_sz...@nbc.gov wrote:
Either add a way to increase the logging sent to syslog with some sort
of flag and/or add a feature to create an informational log.
I guess it's hard to find a solution that fits everyone. That's why I
added a minimal logging (date/time: patch X installed) to
Hi,
However I ran the commands and here is the output:
# uname -a
SunOS Enterprise 5.10 Generic_118833-36 sun4u sparc SUNW,Ultra-80
# showrev -p
No patches are installed
# pkginfo -x
...
That's what I was suspecting - the list of installed patches and
packages is incomplete. Your
Hi Gerard,
# /etc/scripts/pca -i 137137-09
...
calypso-root% /etc/scripts/pca -l 140774
There is a small but important difference between these two commands.
One time you are specifying a patch ID plus revision, the other time
just a patch ID.
In the first case, pca will not look at
Hi,
I am really getting addicted to this sweet program.
It's always great to hear that :)
1. It looks like even if I use the -X option to specify a location
where we have the patchdiag.xref file, the program attempts to
download the Sun's xref file.
Glenn already pointed you at the
A new release of PCA has just been published. Here's a list of
new features and changes:
* Allow search patterns for synopsis to be used with --ignore
* Maintain last modification time on patchdiag.xref and pca
* Add Last-Modified header in local caching proxy mode
* Preserve last
darcy_r_li...@nbc.gov wrote:
We do not have a separate /usr Its part of /.
Ok, thanks. It's interesting that the same problem had been seen with
Solaris 8 a long time ago as well, see Sun Alert 201027:
http://sunsolve.sun.com/search/document.do?assetkey=1-66-201027-1
I'm out of ideas.
Don O'Malley wrote:
I cannot reproduce this problem on my Solaris 9 Update 8 system:
I tried the same now. Installed 115545-04 on an otherwise fully patched
Solaris 9 9/05 system. The init 0 right after patch installation
worked fine.
I'll add one more question for D'Arcy - do you have a
Don O'Malley wrote:
These patches were created, based on the assumption that a customer
would not have both StarOffice StarSuite products installed on the
same box, at the same time.
You're describing a different problem here.
Laurent has OpenOffice 3.0 installed on his machine, and neither
Randal T. Rioux wrote:
Patches away. Happy and well. Reboot machine and I get this message:
Boot device: /p...@1f,4000/s...@3/d...@0,0:a File and args:
Boot load failed.
The file just loaded does not appear to be executable.
{0} ok
Maybe one of these Sun Alerts can help:
Laurent Blume wrote:
Confirmed:
Thanks!
It still displays them:
139337 -- 01 -S- 1 StarOffice 9 (Solaris_x86): Update 1
139338 -- 01 -S- 1 StarSuite 9 (Solaris_x86): Update 1
Hm, so what does pkginfo | grep oobasis show? If possible, just send
me output of:
uname -a uname.out
Hi,
I do have a sun support contract and I am failing to download patch on this box
...
Reusing existing connection to sunsolve.sun.com:80.
HTTP request sent, awaiting response... 500 Internal Server Error
2009-02-04 17:02:01 ERROR 500: Internal Server Error.
Everything's fine with pca, wget
Hi,
Connecting to localhost|127.0.0.1|:3128... connected.
Proxy request sent, awaiting response... 403 Forbidden
11:18:21 ERROR 403: Forbidden.
I assume you already checked whether the web proxy on localhost is
working fine (with some other application than pca/wget)? It's
impossible to say
Hi,
The DEBUG I attached before is debug level 1 output from the
/tmp/pca-proxy-debug.txt
Right, I didn't notice that. So pca-proxy.cgi runs, and looks for an
update to pca because update=auto. It uses wget to get a current copy
of pca from the pca server, going through your local proxy on
Hi,
Would it be possible to add logging to pca, IE- when a recommended
cluster patch set is run, it creates a log file in
/var/sadm/install_data. Can pca be altered to create a log file with
all the patches that were installed in a similar fashion ?
pca sends messages for every installed
Mike J wrote:
Did reboot -- -r between runs of pca (now at 20090112-01) but 18 fail
(repeatedly) with missing patch file errors.
Is it only non-security patches which are failing to download? Without a
support contract connected to your Sun Online Account, the subset of
patches you are
Stephen,
I noticed the email about restrictions in patch usage - is this
related, do you think?
With a free SOA (no support contract attached) you should at least be
able to download all patches that carry the S (security) flag. To make
pca show only this sub-set, you can run pca -l
Hi Stuart,
I'm testing a new X4150 as a SunRay server. The current
version of PCA lists a SPARC SunRay (and the x86 one also)
patch as missing:
...
139548 -- 01 --- 2 Sun Ray Core Services version 4.1 Patch Update
139549 -- 01 --- 2 Sun Ray Core Services version 4.1 Patch Update SunOS
ehab aziz wrote:
I have failed patches that failed to be downloaded for reason I do not know
I just tried, and the patches downloaded fine for me. Have you retried
in the meantime? If it still doesn't work, send me output with pca's
--debug option added.
Martin.
A new release of PCA has just been published. Here's a list of
new features and changes:
* Enable syslog messages to daemon.notice by default
* Enhance possible values for syslog option
* Log sample message to syslog in debug mode
* New generic handling of unknown, non-Sun patches
*
In Solaris 10, the wget includes SSL support, so it needs the SSL
libraries under /usr/sfw/lib ($BASE/usr/sfw/lib in your example). These
libraries are not normally included on the jumpstart minimal OS from my
experience, though I haven't looked at U6.
I think I once used a non-SSL version
Jamen,
I'm really confused. I cannot even get smpatch to work. It keeps looking
for /var/sadm/pkg or /var/sadm/patch, and neither directory exists on
this server. All of our patches are in the /apps directory -
/apps/sadm/pkg and /apps/sadm/patch.
So that's your problem. I assume that the
Michael,
For some reason or the other, Sun SSHD got deinstalled and
then the original, unmodified sshd packages (ie. SUNWsshcu
and friends) got reinstalled from the S10U5 DVD.
Now the patches (eg. 128318-01) are of course missing.
How would one go about re-installing missing patches?
As far
A new develop version of PCA has just been published. Changes:
* Rename internal function err() to avoid keyword clash with recent perl
Martin.
Richard,
If I run pca -l all I get a lot of NOT FOUND IN CROSS REFERENCE FILE!
Should I continue to worry about them :-)
No need to worry about them, you will see them on any Solaris update
release. A quote from http://blogs.sun.com/patch/date/20080609:
There are a number of special or
Richard,
Could you add a flag to ignore them as I want to automatically run
pca-L all and e-mail the results to a web server so we have a vie on
the patches install on all our system in Infineon.
I wouldn't want to add an extra flag for that, but that's not necessary
anyway. Try one of
Nilesh,
I know it's real easy to install this however I want some good scenarios of
PCA implementation. Mostly I am in need of technical information on how to
configure, how to get reports email etc.
To begin with, there's some information in the Contrib section on pca's
webpage:
Michael,
It would be very helpful, if PCA could also display the
„requested revision“ of a patch.
I've always hesitated to add this as it would pretend to give
information which is actually not there. As there is no information
about past revisions in the xref file, pca can't show that
Jeff,
Is there some .pca command that I can add to say don't remove?
Not as of now. Maybe you can just get used to run pca -di instead of
pca -i.
As you seem to patch multiple machines and already try to maintain some
global patch repository, I definitely recommend thinking about setting
Jan Holzhueter wrote:
xref file is updated to install this patch before 137137-09 is applied.
They've done that in a clever way. Instead of publishing a new revision
of 137137 (which would include that dependency), they published a new
revision of 138866 (which is required by 137137) and
Martin Paul wrote:
Thomas Bleek wrote:
The older file gets installed last by pca.
I missed the fact that 138241-01 requires 138217-01, so there's at least
a defined relationship between the patches - you can only install them
in one order.
Sun is looking into the issue as to why the file
Cromwell, Ray, VF-IE wrote:
Is it possible to create a patch list which only list patches which
do not require a reboot using the showrev,uname,pkginfo ?
Unfortunately not. The problem is that the necessary information is not
included in the patchdiag.xref file, but only in the patches
Dagobert Michelsen wrote:
Am 28.11.2008 um 11:56 schrieb Martin Paul:
The fact that patch properties are missing is one of my biggest gripes
about the xref file.
How about adding a feature that generates a patchdiag.xref+ file
on the proxy with information from the patches added?
It's
Ray,
I have attached a copy of the file in question .
The mailing list software didn't let the attachment through (too big),
but we don't need it on the list anyway. Look at the end of the file:
## Additional entries for the patchdiag.xref file ##
## Maintained by the TLP-Team
Jan Holzhueter wrote:
I installed a Solaris 8 10/01 s28x_u6wos_08a INTEL
today and tried to patch it.
Great - Solaris 8/9 on x86 are missing in my test machine zoo, so I
don't have on-hand experience with those.
Went well except for:
114147 -- 01 -S- 999 SunOS 5.8_x86: Supplement Kernel
ehab aziz wrote:
What is the contract Id ? Is it the order number OR the serial number that I
receive ? Or I should wait it for 5 business days ? I tried all in the field
*Sun Service Plan *
*All are not accepting !!*
It's been a long time since I got a support contract, so I don't
A new release of PCA has just been published. Here's a list of
new features and changes:
* Read only pca-proxy.conf (not pca.conf) in proxy mode
* Provide more detailed exit status
* Include patch count and sum of patch ages in header
* Fix handling of downloaded files that are too short
*
Fred Chagnon wrote:
In my wrapper script for pca, I would like to be able to determine if pca
finished patching completely, or if it finished prematurely, perhaps due to
a patch that required an immediate reconfigure reboot. Does pca have
different return codes for these situations? Where can I
Laurent Blume wrote:
With the release of SunSolve in October 2008, ...
This sounds like a bigger change on sunsolve.sun.com, so this really
might be the root cause. I've sent a message to Gerry Haskins, but he's
currently out of the office.
Thanks for the link to the InfoDoc - I didn't
Martin Paul wrote:
* Check whether patch already exists before announcing download
If a patch already exists in patchdir, it will not say anything about
Downloading .. anymore. Let me know if that's OK for you.
I discovered that this change had some ill side effects with parallel
patch
David Stark wrote:
We've got a bunch of machines with EBS clients installed, and every pca run
results in:
116831 -- 04 -S- 647 Sun StorEdge EBS 7.2: 32-bit Product Patch SU3
being recommended. This fails with:
I have found the reason for that; the EBS patches use sparc and
sparcv9 in the
David,
Seems as if the EBS patches use an unusual method to deliver 32/64 bit
patches; e.g. they list sparcv9; in the architecture column within
xref, where all other patches list only sparc;. This is only part of
the problem. I'll need some more time to dive into this ..
Martin.
Hi,
Currently, my wrapper, filters the output of pca -i missing for the
Engineer who is installing the patches, as he/she will get confused as the
patch bundle was generated and why PCA is attempting a download when we are
trying to install the patches.
I think I understand now what you're
Hi,
Is there a way to avoid this attempt of download and directly install the
patch from the directory mentioned in patchdir option?
As Michael already stated, pca won't attempt to download the patch again
if it already exists. It *does* show Downloading .., but this really
means the whole
Hi,
Recently I noticed that some host was daily downloading 100's of copies
of pca from our server within a few minutes, causing quite some network
traffic. I tried to contact [EMAIL PROTECTED] by e-mail, to no avail. I
added the IP address to apache's .htaccess file, but it kept on trying.
Evan,
Good morning...or is it already your afternoon?
It's 15:30 here .. so I'm nearly done with my daily tasks already :)
in other words, my own tool was preventing pca from working
I see. At least I know that I asked the correct questions, it's just
that you didn't answer them right
Ray,
Is there a way to only list installed , Recommended security using
a local showrev/uname/pkginfo.
It should work just the way you tried it. Look here:
$ pca -l installedrs | wc -l
121
$ uname -a uname.out
$ showrev -p showrev.out
$ pkginfo -x pkginfo.out
$ pca -f . -l
Cromwell, Ray, VF-IE wrote:
Sorry paul, left out the header --
./pca -f . -l installedrs
Using /var/tmp/patchdiag.xref from Sep/23/08
Host: iecsai33 (SunOS 5.10/Generic/sparc/sun4u)
List: installedrs
And blank from here on !
And you're sure that there are some R/S patches installed on
Hi,
Downloading 119254-58 (1/274)
Trying http://sunsolve.sun.com/ (1/1)
substr outside of string at /path/to/pca/pca.pl line 740.
Use of uninitialized value in string eq at /path/to/pca/pca.pl line 740.
Failed (unknown file type)
This tells me that pca received a file from sunsolve which is
Hi,
Reusing existing connection to sunsolve.sun.com:80.
HTTP request sent, awaiting response... 200 No headers, assuming HTTP/0.9
Length: unspecified
Here's where things go wrong. The web server on sunsolve.sun.com
obviously returns an unexptected reply (without any HTTP headers?).
Are
Hi,
Sorry for the delay; I've been out of office during the last days.
Is anyone else getting errors like the following when running PCA on
a system using ACSLS?
That's a kind of patch ID which I (and pca) haven't seen before. I've
modified the development release of pca to recognize it.
Marque de Courten wrote:
PCA found two patches, 120011-14 and 127127-11 and failed to install
them saying that these patched are already installed. Any ideas how to
fix this?
That's probably because of this change in pca:
* Check for patches which are only partly installed
see:
A new release of PCA has just been published. Here's a list of
new features and changes:
* Remove check for patches which are only partly installed
Update:
pca --update now
Download:
http://www.par.univie.ac.at/solaris/pca/installation.html
MD5: c884c226291d73d091f16a091b36f8f8
Fredrich Maney wrote:
What about instead of using a separate --pattern flag that you make
it so that --ignore, --rec and --sec accept patterns or add flags
for ignorepattern and requirepattern?
Yes, I've been thinking about a more general solution to this as well.
Similar to your idea I've
A new release of PCA has just been published. Here's a list of
new features and changes:
* Check for patches which are only partly installed
* Fix bug with missing patches with multiple versions of the same package
* Log failed patch install to syslog
* Fix minage option being one day off
*
As for pca updates with a pca proxy there are two things:
Updating pca-proxy.cgi: If you have update=auto set in the pca.conf
used by pca-proxy.cgi, the proxy will keep itself up-to-date. It will
download and replace itself with new version of pca when they are
available. pca-proxy.cgi should
Floyd, Chuck wrote:
Is there a way for me to put in multiple pattern matches? For example,
I want to match Veritas patches with VRTS|VERITAS|Veritas|SYMC but not
NetBackup.
Unfortunately not. You can only combine your pattern with ignore
statements for all the NetBackup patch IDs that match.
Hi,
Has anyone had any problems patching Solaris 10 .
Server had problems installing allot of patches which pca recommended .
Your machines obviously runs a pretty old version of Solaris - I hope
it's not one of the beta versions. /etc/release should tell you.
Installing 118833-36...
Some of you might know that there's a problem with the Solaris patch
system which has not been fixed by pca yet:
Assume a patch applies to pkg1 and pkg2, and only pkg1 is installed.
Installing the patch will fix pkg1 only. If you install pkg2 later, the
fixes from the patch for this pkg will
Hi Laurent,
I'm a bit unsure what to make of this.
I have a suspicion that pca might have problems with two versions of the
same package installed. As the set of package names is not exactly the
same for Studio 11 and Studio 12 this could result in only some of the
patches not being shown.
Laurent Blume wrote:
There's another weird thing I just noticed, not sure if it's related.
I had to install 127153-01 manually (unzip had a non-zero return because
the zip contains extra data).
The copy of 127153-01 I have on my pca proxy is fine:
$ ls -l 127153-01.zip
-rw-r--r-- 1
Laurent Blume wrote:
Martin Paul a écrit :
I have a suspicion that pca might have problems with two versions of the
same package installed. As the set of package names is not exactly the
same for Studio 11 and Studio 12 this could result in only some of the
patches not being shown. Can you
Laurent Blume wrote:
Martin Paul a écrit :
If you are up-to-date on patch*/pkg* command patches, you probably
should report this to Sun.
*sigh*
I have to check if the problem can be reproduced on a more up-to-date
system
I found this BugID:
6479605: pdo must behave like patchadd
[EMAIL PROTECTED] wrote:
If you're always using an out of date patchdiag.xref file, how can you tell
what patches you're behind on on every client machine? I think the main issue
I'm having is that I want to compare to BOTH the latest and a specified
baseline on every client.
You really
Dagobert Michelsen wrote:
I think providing archived patchdiag.xref versions from your site would
be a valuable service for the PCA users ...
I'd better not. The SLA, which you have to accept before accessing
SunSolve, says:
Software and Information are the confidential information of Sun
Christoph Litauer wrote:
I used to use option --noheader (-H) in my pca wrapper script ... and
wondered why my machines didn't even reboot after a kernel patch. As far
as I debugged it --noheader suppresses reconfigure or reboot
messages at all. The manpage doesn't mention that, I think it
Hi,
well, extended is maybe a bit too exaggerated for my suggestion, but I
think it would be neat if pca would also report failed patch installs or
even failed downloads in addition to reporting succesful installs.
My idea was to log only things which actually modify the system to
syslog;
Hi Willi,
on my SPARC SunRay Servers pca shows me a x86 patch:
127554 -- 03 --- 81 Sun Ray Core Services version 4.0 SunOS 5.10_x86 Patch
Update
How can I clean up this misbehaviour?
I've already put a workaround for the 127553/127554 patches into pca.
Just update your copy of pca to
Hi Ray,
I have the appropiate entries in pca which I copied from previous
version .
wgetproxy||s|URL|http://10.162.?.?|Default proxy for wget,
proxyuser||s|PRUSER|???|Proxy user for wget,
proxypass||s|PRPASS|???|Proxy pass for wget,
So you've made local modifications to your copy of pca,
Jonathan,
Not being an experienced user of pca it did not immediately occur to me
that pca would also patch Netbackup, can anyone suggest the best method
of excluding patches for a particular application?
If you don't want to use the ignore option, you can alternatively use
the pattern
Hi,
Is there any way I can force pca to only apply the recommended and security
patches?
Read about patch groups in the OPERANDS section of the docs. The default
is missing, which means all missing patches. You can add r and/or
s to restrict this to a subset.
pca -l missingrs would list
I assume that this wont stop the kernel patches clobbering sendmail tho.
No, which is just one of the problems with Sun stuffing application
patches into the kernel patch. Another is the inability to backout e.g.
just the sendmail fixes if you don't want them (buggy patches are
nothing
Uhhh, kernel patches don't touch sendmail -- sendmail patches do.
Unfortunately this isn't true anymore. E.g. here's a list of patches
which include /usr/lib/sendmail:
118833-36: SunOS 5.10: kernel patch
118855-36: SunOS 5.10_x86: kernel patch
120011-14: SunOS 5.10: kernel patch
120012-14:
Greg Matthews wrote:
Martin Paul wrote:
Greg Matthews wrote:
looks like a mismatch between kernel and modules. I rolled back the
kernel patch from 137111 but the undefined symbol problem persists.
Is 137111 the only kernel patch during you patching session? There are
118833, 120011
Just found the below information on Sun's Sun Update Connection Forum.
Patch downloads using pca might be affected as well:
NOTICE OF PLANNED OUTAGE:
Sun patch update services will undergo planned maintenance this Friday
(1 August 2008) from 1900 EDT to 2300 EDT.
Customers may not be
Hi,
and (after about 3 minutes) 2 thousand processes running.
...
webservd 7467 7466 0 11:25:34 ? 0:00 /usr/sfw/bin/wget -q
-O /tmp/README.137111-0412174963347462 http://ftp.gfz-pots
It seems as if the proxy is contacting http://ftp.gfz-pots..; to get
the README instead of
Hi,
Sorry, but I did not realize that this was a problem.
Not your fault - the current behaviour really isn't what you would
expect. I think I'll soon break backwards compatibility and make
pca-proxy only read pca-proxy.conf in the future.
BTW.: Is it ok to set a softlink from
A new release of PCA has just been published. Here's a list of new
features and changes:
* Workaround for 120011/120012 requiring obsolete patches 122660/122661
* Fix a bug when using current version of wget with https
* Enhance checks for empty or corrupt patchdiag.xref file
* New default
Laurent,
It's strange, because I patch those systems with R/S patches once a year
at least. So, is it possible that this patch wasn't recommended last
year, and now is?
Yes. I've checked some of the old patchdiag.xref files I keep - the R
attribute has been added to this patch sometime
Rajiv Gunja wrote:
Yes, I do agree that most of us rarely backout patches in any kind of
environment. But I have couple of servers which does not have extra disks
for me to use LU Patching or use an Alt-Boot. So was wondering if there was
an option to backout patches using pca.
There is no
Rajiv Gunja wrote:
You will see that there is no Version of Solaris information on that line.
PCA just uses this information to enlist the patch as needed/required.
Exactly - there's no way for pca to determine that these patches are for
a special OS release only, judging from the
Hi,
Is there a way to install recommended patch cluster using pca?
Using the cluster or using pca are two different philosophies of
patching, so the question doesn't make much sense.
The Recommended Patch cluster is a set of patches prepared by Sun in a
bundle which contains most of those
Chris Coffey wrote:
Or something similar where files/perms/links aren't kosher to proceed with a
patch. I think this is related to using the safe switch, is that correct?
Correct. Don't use the safe option, and the errors will be gone. You
provide a good example of what --safe can do for
Paul B. Henson wrote:
That used to be the case with Solaris express. However, supposedly for the
new openSolaris distribution each release will be supported for 18 months,
including back porting of security and bug fixes:
http://www.sun.com/service/opensolaris/index.jsp
I had read
Ray Van Dolson wrote:
On Wed, Apr 30, 2008 at 05:00:41PM -0400, Mike Moya wrote:
it appears that if you have a mounted/exported file system this patch
will not install. You get the following error:
mount: Mount point /var/run/.patchSafeMode/root/home/xxx/a does not exist.
Interesting. I
Hi,
Is there a way of completely blacklisting a patch in PCA without
editing the script itself? --ignore (according to the docs, I've not
had a chance to test) will apply an ignored patch if it's a
dependency of another patch, so that may not work for us.
Yes. I'm not too happy about that
Maybe something like a '--never=' option to avoid breaking the existing syntax?
Adding new more options is the one thing I hate even more than breaking
existing behaviour :) We'll see - other options are affected as well;
e.g. when specifying to show only missing security patches
I just put a new development release of pca online, with this change:
* Add option for concurrent patch downloads (--threads=NUM)
It's a rather big change in code actually - I've finally integrated the
patch by Chris Reece which he made available at:
http://www.sparsezone.com/pca/
It
Don Solberg wrote:
I have started using PCA on a new Sun M5000 Solaris 10 U4 server and
all patches well. The issue is a reboot after the patch
installation, the sever appears to hang, finally continuing to reboot
over an hour later. It appears to hang on the process on shutting
down on the
401 - 500 of 503 matches
Mail list logo
