[Bug 12855] New: Scripts that support logging should enable logging by default
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 Bug ID: 12855 Summary: Scripts that support logging should enable logging by default Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs@lists.koha-community.org Reporter: martin.renvoize@ptfs-europe.com QA Contact: testopia@bugs.koha-community.org CC: robin@catalyst.net.nz It's only when somthing goes wrong that you tend to start looking for the logs.. so logging should be set at a sensible level by default. For instance, the fines.pl script supports logging but it is disabled by default. I believe this is wrong, logs should be enabled, directed to /var/log/koha/instance whatever and logrotate used to manage them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, I think I disagree and the logging had been turned off by intention. I think we shouldn't put files with patron sensitive information on the server by default, when the library might not be aware of it. It should be opt in... not opt out. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hm, also there is logging on the database side if you have FinesLog activated. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 --- Comment #3 from Robin Sheat <robin@catalyst.net.nz> --- Logging should be set up like most things do it: errors, warnings, info, debug levels. My suggestion is that default, errors (and warnings?) are logged, however are checked to ensure that they won't divulge sensitive information, but is able to give you a heads-up to say that something might need checking out. Also, they should use something like Log::Any or Log4Perl to do it properly, none of this spamming syserr/sysout like some scripts do. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi Robin, makes sense to me. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org