http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12952
--- Comment #1 from Srdjan Jankovic <[email protected]> --- Log transactions (actions) to syslog facility. The reason being to enable external tools that can parse log files to get their fingers on the action log. The alternatives are: 1. Use Log::Any or similar. I did not go for this one because it is a bit hard to retrofit a beast like that, and then we are potentially entering into configuration nightmare. 2. Log straight to <log dir>/action.log. That was a hard decision, and the approach is more or less equivalent to the proposed one. I believe syslog gives a bit more flexibility. Parts of the proposed solution that deal with syslog config are debian/rsyslog based, but those can easily be adopted in other environments. I'm open for discussion/suggestions. -- You are receiving this mail because: You are the assignee for the bug. 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/
