Hello,
This has been discussed before, see the thread from March 2010 [1] and possibly
earlier threads.
On Jan 4, 2011, at 11:58 AM, Juan Antonio Martinez wrote:
> El lun, 03-01-2011 a las 13:01 +0100, Viktor TARASOV escribió:
>> Hi,
>>
>> I propose to introduce the following short form to insert debug messages of
>> the 'normal' level.
>> Any objections?
>
> Fine, but thinks that we need a way to get finer debug tuning:
>
> Not sure... perhaps it's time for introduction of a syslog(2) style
> debug levels (ALERT,CRIT,ERR,WARN,NOTICE,INFO,DEBUG,TRACE and so);
> or better, think in a way to set specific debug levels per item
> ( as log4c/log4j does )
My personal opinion is that logging is for (long-running) services (think:
Apache request log, SSHD authentication failures etc) to leave a "paper trail".
OpenSC logging is a debug log which is either for cases where something breaks
for an end-user and we need to have a look what where and why ("I have a
problem, XXX does not work" => "Please re-do your problem with logging enabled
in opensc.conf") or for lazy developers using the log instead of a debugger or
as a complimentary information source when using the debugger.
Going for log4c or similar would IMHO be a total overkill, as is implementing
anything internal that is designed for RFU. Focus should be on things related
to smart cards, not logging :)
If you want debug logging, too much is better than too little (you can always
use grep). Under normal conditions, OpenSC should not leave a log ("User
entered a PIN", "User signed some data" makes no sense).
[1] http://www.opensc-project.org/pipermail/opensc-devel/2010-March/013651.html
--
@MartinPaljak.net
+3725156495
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
