Professional Web Applications Themes

patch cluster feature request - Sun Solaris

Tony Curtis wrote: > 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? > > t What's wrong with /var/sadm/install_data/<cluster_name>_log ?...

  1. #1

    Default Re: patch cluster feature request

    Tony Curtis wrote:
    > 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?
    >
    > t
    What's wrong with /var/sadm/install_data/<cluster_name>_log ?


    John Salvo Guest

  2. #2

    Default Re: patch cluster feature request

    >> On Tue, 29 Jul 2003 03:40:00 GMT,
    >> John Salvo <jmsalvo.au> said:
    > Tony Curtis wrote:
    >> 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? t
    > What's wrong with
    > /var/sadm/install_data/<cluster_name>_log ?
    Nothing per se, it's just that sometimes I am patching the
    system in single-user mode remotely through a serial
    connection and it would be nice to see a progress
    indicator in that window.

    t
    Tony Curtis Guest

  3. #3

    Default Re: patch cluster feature request

    Tony Curtis <tony_curtis32> wrote in message news:<87r84af15u.fsflimey.hpcc.uh.edu>...
    > >> On Tue, 29 Jul 2003 03:40:00 GMT,
    > >> John Salvo <jmsalvo.au> said:
    >
    > Tony Curtis wrote:
    > >> 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? t
    >
    > > What's wrong with
    > > /var/sadm/install_data/<cluster_name>_log ?
    >
    > Nothing per se, it's just that sometimes I am patching the
    > system in single-user mode remotely through a serial
    > connection and it would be nice to see a progress
    > indicator in that window.
    >
    > t
    >
    tail -f /var/sadm/install_data/<cluster_name>_log

    and you can see the progress...
    kgyula@mailcity.com Guest

  4. #4

    Default Re: patch cluster feature request

    Tony Curtis wrote:
    >>>On Tue, 29 Jul 2003 03:40:00 GMT,
    >>>John Salvo <jmsalvo.au> said:
    >
    >
    >>Tony Curtis wrote:
    >>
    >>>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? t
    >
    >
    >>What's wrong with
    >>/var/sadm/install_data/<cluster_name>_log ?
    >
    >
    > Nothing per se, it's just that sometimes I am patching the
    > system in single-user mode remotely through a serial
    > connection and it would be nice to see a progress
    > indicator in that window.
    >
    > t
    ../install_<cluster_name> &
    tail -f /var/sadm/install_data/<cluster_name>log

    ?



    John Salvo Guest

  5. #5

    Default Re: patch cluster feature request

    >> On Wed, 30 Jul 2003 02:19:30 +1000,
    >> John Salvo <jmsalvo.au> said:
    > Tony Curtis wrote:
    >>>> On Tue, 29 Jul 2003 03:40:00 GMT, John Salvo
    >>>> <jmsalvo.au> said:
    >>
    >>> Tony Curtis wrote:
    >>>> 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? t
    >>
    >>> What's wrong with
    >>> /var/sadm/install_data/<cluster_name>_log ?
    >> Nothing per se, it's just that sometimes I am patching
    >> the system in single-user mode remotely through a
    >> serial connection and it would be nice to see a
    >> progress indicator in that window. t
    > ./install_<cluster_name> & tail -f
    > /var/sadm/install_data/<cluster_name>log
    Yes, but neither output shows how *far* into the patch
    sequence you are. Currently I compare the output with the
    patch_order file, but adding a count-o-meter to
    install_cluster is trivial and would make it obvious how
    many patches remain.
    Tony Curtis Guest

  6. #6

    Default Re: patch cluster feature request

    > Yes, but neither output shows how *far* into the patch
    > sequence you are. Currently I compare the output with the
    > patch_order file, but adding a count-o-meter to
    > install_cluster is trivial and would make it obvious how
    > many patches remain.
    I must say that I like the idea, it gives you a good overview how far
    the patching is.
    When you need to install patches on mutiple sun's this would be very
    handy!
    John Guest

  7. #7

    Default Re: patch cluster feature request

    > 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.




    Oscar del Rio Guest

  8. #8

    Default Re: patch cluster feature request

    >> On Wed, 30 Jul 2003 12:49:33 GMT,
    >> "Oscar del Rio" <delriomie.utoronto.ca> said:
    > 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.
    It does seem to be fairly standard, but I thought I'd
    spread the joy amongst y'all :-)

    It's such a trivial addition, and at least IMHO would add
    so much good-vibe-feeling to the process.

    (Someone from Sun already contacted me and said they'd
    submitted a feature request for it.)

    t
    Tony Curtis Guest

Similar Threads

  1. How to report bug or request new feature
    By robinbak in forum Macromedia Flex General Discussion
    Replies: 1
    Last Post: February 23rd, 03:19 AM
  2. NAME SPACE REQUEST: Cluster::Run
    By Zak Zebrowski in forum PERL Modules
    Replies: 0
    Last Post: April 14th, 12:56 PM
  3. Feature Request for FW6
    By mike in forum Macromedia Fireworks
    Replies: 1
    Last Post: August 23rd, 12:06 PM
  4. Patch Cluster & Kernel Panics
    By Frank Batschulat in forum Sun Solaris
    Replies: 0
    Last Post: July 19th, 02:50 PM
  5. New Feature Request
    By Cheesefood in forum Adobe Photoshop 7, CS, CS2 & CS3
    Replies: 2
    Last Post: July 17th, 11:56 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139