http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8066

Chris Nighswonger <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
                   |                            |u

--- Comment #5 from Chris Nighswonger <[email protected]> ---
(In reply to comment #4)
> (In reply to comment #2)
> > I disagree. I think most people expect the logs to be populated by default.
> 
> Most people who *know* there are logs expect them to be populated by
> default. However, small libraries, will never know. And I think it's much
> more harmfull to have them ON by default than to discover it would have been
> useful to have them ON and discover they're OFF ! If the cleaning was
> automatic, I wouldn't object. But it's not the case, and we have discovered
> that one of our small customer had ... 2 millions lines in this log, for a
> database of less than 10k items !

I expect logs to be enabled by default. This is consistent with nearly 100% of
software which I have had experience with, including all *nix packages.

I think that this is more of a training issue than a software issue. Train
librarians/system admins to check/truncate/archive/whatever their logs and this
problem will go a way.

I would not be opposed to some sort of auto-archiving feature similar to what
*nix logs typically have.

My $0.02 worth...

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to