[pca] Logging
Martin Paul
martin at par.univie.ac.at
Thu Feb 26 09:48:29 CET 2009
Hi Ben,
> I am uncertain how an added Option flag is forcing anything on anyone.
> People do not have to use it, being optional.
It's not forcing anything on anyone, and high flexibility usually is a
good thing. But at the same time an overload of options can drive people
away before they even start to use it. Lately I'm with Antoine de
Saint-Exupéry, who said: "It seems that perfection is reached not when
there is nothing left to add, but when there is nothing left to take away."
> I did not see any logging for positive states in syslog. Only failures.
> So that might be a bug.
That's strange. pca does log both successful and failed attempts to
syslog, to the same facility/level. Please try that again.
> Pca is not a small tool. Nor would it be overkill to add a logging
> mechanism. In my opinion.
I appreciate that. And it's one more step towards convincing me that
more detailed logging is necessary. I'm just not there yet :)
> Example of /var/sadm/spool/sunucLog/job_history.log
Thanks. Ok, now that's exactly what I would not want a log look like. At
least half of the messages don't seem to contain real information. And
with that many failures, errors, warnings etc. I definitely would do my
patch installs interactively, watching the output on screen.
In my experience (and not to sound arrogant) with pca it really boils
down to one "successful install"-message per patch, so for 99% of the
pca runs I wouldn't know what more information to include.
Martin.
More information about the pca
mailing list