[pca] Logging
Ron Halstead
rdhalstead at gmail.com
Fri Feb 27 17:47:52 CET 2009
You want logging, you got logging:
# Download and install the patches.
pca --nocheckxref \
--patchdir=${PATCHDIR} \
--xrefdir=/patches/pca/htdocs/${ROLE} \
--patchurl=http://${SERVER}/${ROLE}/pca-proxy.cgi \
--xrefurl=http://${SERVER}/${ROLE}/pca-proxy.cgi \
--fromfiles=${TMPDIR}/${HOSTNAME}_ \
--install $PATCHGRP | tee -a ${LOGDIR}/${HOSTNAME}.patchlog.`date
+%y%m%d` 2
>&1
--ron
__________________________
Ron Halstead
Senior UNIX Systems Analyst
rdhalstead at gmail.com
__________________________
Martin Paul wrote:
>
>> 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 else to log for a successful patch
> install. For a failed patch install, I could only log full patchadd
> output (no way to extract just useful messages), and that can be 100s
> of lines for e.g. a kernel patch.
>
> Martin.
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rdhalstead.vcf
Type: text/x-vcard
Size: 354 bytes
Desc: not available
Url : https://lists.univie.ac.at/mailman/private/pca/attachments/20090227/ca3362cf/attachment.vcf
More information about the pca
mailing list