Would you accept something like appending the new configuration bit on
already created instances? During upgrade?
for i in $(koha-list); do
cat "the entries" >> /etc/koha/sites/$i/log4perl.conf
done
The same will happen for SIP and other targets...
Oh, and I noticed we didn't consider this for the Z39.50 responder :-/
El lun., 16 mar. 2020 a las 16:55, Tomas Cohen Arazi (<tomasco...@gmail.com>)
escribió:
> Hi all. I'm not that familiar with our Koha::Logger class usage, but I
> noticed there's no 'api' target and it would be handy to have it. There's a
> bug for a 'sip' target and for other things. It looks like the main reason
> for adopting log4perl was the flexibility it provided, and it makes sense:
> many appenders, several options, centralized config, etc.
>
> The question is: how do we update people's config? We cannot just go edit
> their configs, right? The current log4perl.conf on each instance is
> generated using the template and adjusting the instance name.
>
> Has anyone thought about this update problem? Ideas?
>
> --
> Tomás Cohen Arazi
> Theke Solutions (http://theke.io)
> ✆ +54 9351 3513384
> GPG: B2F3C15F
>
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
