[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
Hi Martin,
Am 28.08.2008 um 11:37 schrieb Martin Paul:
[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
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
Hi,
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 should?
--
Regards
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
Martin Paul schrieb:
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
Well, isnt it obvious that PCA has become such a good competitor to smpatch
and their weird TLP that they do want to restrict the use or distribution of
patchdiag.xref file.
However it is freely available to everyone, with or without a sunsolve
account on their website, so not sure what they are
