[pca] Running summary

[Rajiv Gunja]

This is my blog: http://ossrocks.blogspot.com

-GGR

--
Rajiv G Gunja
Blog: http://ossrocks.blogspot.com


On 23 February 2010 11:59, Ron Halstead <rdhalstead at gmail.com> wrote:

> Rajiv,
>
> I too have written a wrapper that includes timestamps and totals. I would
> be interested in comparing mine to yours. What is the URL to your blog. You
> did not include it.
>
> Ron Halstead
>
> Rajiv Gunja wrote:
>
>> Craig,
>> What you are asking for can be easily done using a wrapper script. I too
>> needed a simple output to the tty as I did not want the Engineer to have to
>> look at so much of data scrolling on their screen. A simple output showing
>> what is being installed and if there are any errors or failure it should be
>> visible within the scroll length of the Engineer's screen. So I wrote my own
>> wrapper around PCA. In my wrapper script I filter out all patching output to
>> a log file and show only the patch being installed and how many are
>> remaining. It would not be much difficult to add a time stamp to that.
>>
>> If you are interested, please look at my blog where I have published all
>> the scripts I use around PCA. The "installpatch.sh" is the script you might
>> be interested in.
>>
>> My output looks like this:
>>
>> <root at agni40> ./installpatches.sh
>> Are you installing these patches in Single User Mode? [y,n] n
>> Specify your Alternate Root Directory: /PBE
>> Installing Patches to ABE: /PBE
>> Installing 119254-64 (1/138)
>> Installing 118666-18 (2/138)
>> Installing 119059-46 (3/138)
>> Installing 119117-47 (4/138)
>> Installing 138217-01 (5/138)
>>
>> But you can append time stamp to it as it is your requirement.
>> Hope this helps.
>>
>> -GGR
>>
>> --
>> Rajiv G Gunja
>> Blog: http://ossrocks.blogspot.com
>>
>>
>> On 22 February 2010 18:26, Craig Bell <Craig.Bell at standard.com <mailto:
>> Craig.Bell at standard.com>> wrote:
>>
>>      Dear Martin,
>>
>>      A casual request:   Could pca show a brief session summary after
>>    each patch?    Perhaps something like:
>>
>>    “Done -- 12:34:56 PST -- 00:10:30 elapsed, 02:30:40 total -- 103
>>    successful, 1 skipped, 0 failed”
>>
>>      Background:  We monitor each pca session, in case of unforeseen
>>    problems (i.e. /var fills up).  We patch multiple hosts at once,
>>    so it can be difficult to recall the state of each host is along
>>    the way.  As I cycle through all of my terminals, it would aid our
>>    understanding to see interim summaries.
>>
>>      I would find it quite useful to see a timestamp, the elapsed
>>    time for the last patch (and cumulative for the entire run), plus
>>    the running tally of outcomes.   Using “—debug” prints a timestamp
>>    when calling patchadd, but this option is otherwise more verbose
>>    than I care to see during a typical patch run.
>>
>>      We use “--syslog”, so we can still go through the logs
>>    afterwards (unless I forget to start syslog in runlevel S).  I can
>>    also review /var/sadm/patch timestamps, if needs be.  It’s merely
>>    simpler to see all of this distilled in the pca output where I can
>>    follow along live, and keep it handy after the system logs roll off.
>>      I imagine that accustomed users would (understandably) see this
>>    as visual clutter.   Also, I recall that you are careful about
>>    adding new options, so I’m not suggesting another switch.   If you
>>    feel that pca already prints enough information, then I would not
>>    care to spoil this for satisfied customers.
>>
>>      If it’s a matter of degree, then you could use shorthand, as
>>    seen with the list count / age, for example:   “Done
>>    (12:34:56/10:30/2:30:40) -- (103/1/0)”
>>
>>      Thanks in advance for your thoughts on a running status…    -cheers,
>> CSB
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.univie.ac.at/mailman/private/pca/attachments/20100223/317f4221/attachment-0001.html