About default error log : in my opinion we must not activate by default. Because default directory is web accessible. We use some thaccess for apache, but no way for IIS or nginx. Terrible security issue to let log to be readed.
https://manual.limesurvey.org/Optional_settings#Logging_settings

Debug = 2 are not for log :)

maybe we can :

1. Add 'fileError' in internal.php
2. but : set enable to false
3. Put the information in config.php file

Can be part of https://bugs.limesurvey.org/view.php?id=14772 (need to find times on this one)

Else : think there are 2 different issue here.

Maybe you could meet both the security issue and user perception by checking what you're installing on:

if (host = some_unix -linux, android, macos etc) { default log on and located in /var/log/limesurvey/ }
else {log off and goes to ~\tmp\runtime if turned on by the user.}

Lol … no …

Too complex and subject to error in some week.
Since it's easy to update in config.php

My opinion : is :

1. Allow set runtime path when install
2. Add the information about log

if (host = some_unix -linux, android, macos etc) { default log on and located in /var/log/limesurvey/ } no, really no … you can have 500 step of limesurvey on same server. log emplacement can not be auto-dermtimate : it's the admin guys to decide .

PS: php error log still there

you say:
My opinion : is :

Allow set runtime path when install
Add the information about log

--
I like that - assuming you include letting the installer set (or at least see) the log path as part of setting the run-time path and then set debug levels interactively.

I have been using Opensocial (drupal, not MS - https://www.drupal.org/project/social - ) in a social experiment for some time. Their version of the multi-admin problem is that the opensocial host admin creates many sub-admins each of whom is responsible for one ore more user groups. To accommodate their needs to see error msgs generated by their actions without giving them access to the full log, the opensocial developers (like many drupal users) allow the host admin to specify that log msgs go in the database. Sub-admins then access their own error msgs via the normal gui interface.

that log msgs go in the database

Sincerely : i let this for plugin , and here : you talk for a plugin to drupal with specific part and log part …

huh?

je ne comprends pas..

(If you mean you once proposed a plugin to do this, you're way ahead of me and I hope the Limesurvey developers accept the idea. )

No : i mean : not in core, it must not be in core.

Since it's not so difficult to do it in plugin.

I never talk to other LimeSurvey dev to add a DB for log.