[pca] better logging [feature request]

[Ron Halstead]

Here is how I do it:
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

On 10/ 7/11 02:56 AM, dpecka wrote:
> well, it was only proposal .. i know that i can do it by syslog but
> we're using pca also in prod and on many hosts and it's sometimes tricky
> to convince managers that we want to modify syslog on 100 servers ..
>
> well sure, we can use pca|tee but i think that if pca logs by default
> (no additional config) to somewhere it could be useful ... also
> posibility to split pkgadd log and pca own log sounds reasonable to
> me ..
>
> regards, d
>
> On Fri, 2011-10-07 at 11:25 +0200, Martin Paul wrote:
>> Hi Daniel,
>>
>>> i'd welcome if pca could log own activities as well as patchadd
>>> activities in better way then current syslog possibility ..
>> Making PCA log more shouldn't be a problem, but what exactly would be useful? I
>> wouldn't want to direct the complete debug output to syslog, so I need some
>> input here.
>>
>> Originally I restricted logging to the only thing where the system is actually
>> modified - which is when a patch is installed.
>>
>>> think about it please - i believe that some default /var/tmp/pca.log
>>> file will be appreciated by the most of folks.
>> I'm not keen on adding an extra logfile, me being a big fan of collecting all
>> logging in syslog. As Glenn says, you can use syslog.conf to direct PCA's
>> messages to a separate file, and you can set up log rotation in a way that log
>> messages are kept forever.
>>
>> Martin.
>>