Re: patch cluster feature request
From: Oscar del Rio (delrio_at_mie.utoronto.ca)
Date: 07/30/03
- Next message: Tony Curtis: "Re: patch cluster feature request"
- Previous message: Anthony Mandic: "Re: Issues with E3500 running DiskSuite 4.2.1"
- In reply to: Tony Curtis: "patch cluster feature request"
- Next in thread: Tony Curtis: "Re: patch cluster feature request"
- Reply: Tony Curtis: "Re: patch cluster feature request"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 30 Jul 2003 12:49:33 GMT
> To Sun: how about adding a progress counter for install_cluster?
>
> At the moment you just see
>
> Installing 110723-06...
> Installing 110460-30...
>
> or similar. What about?
>
> Installing 110723-06 (104 of 128)...
> Installing 110460-30 (105 of 128)...
>
>
> Could install_cluster also provide a better exit code
> report than just the exit code? The various codes
> (e.g. 2, 8, ...) have meanings, so why not print out the
> explanatory text too?
I think the MU installation scripts do both progress
and error report. I do not know why this has not
been ported to the install_cluster.
If the install_cluster script is always the same (I think
all it does is basically run patchadd for every patch in
patch_order) you could edit the script, save it elsewhere
and run your copy for every patch cluster instead of the
bundled one.
- Next message: Tony Curtis: "Re: patch cluster feature request"
- Previous message: Anthony Mandic: "Re: Issues with E3500 running DiskSuite 4.2.1"
- In reply to: Tony Curtis: "patch cluster feature request"
- Next in thread: Tony Curtis: "Re: patch cluster feature request"
- Reply: Tony Curtis: "Re: patch cluster feature request"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|