TYPO3 Core

I wouldn't remove these information since they are very useful if something goes wrong and you need to know what. Last week we set up a system with one database but multiple web-hosts behind a load balancer and a database locking.
In this case it was really helpful to know, what was going on.

• setup a $TYPO3_CONF_VARS['FE']['logLockActivity'] which is of type boolean and enables/disables the loggin for locking
• use the loglevel for t3lib_div::sysLog, which can be set to INFO, NOTICE, WARNING, ERROR or FATAL - like it's done for other servers on e.g. Linux
  > if the level is NOTICE, everything will be logged; if it's ERROR, only errors and fatal erros will be logged
  > $TYPO3_CONF_VARS['SYS']['systemLogLevel'] addresses exactly this scenario (and is already available)

yes, $TYPO3_CONF_VARS['SYS']['systemLogLevel'] is the best to do.

Would it make sense to set it by default to 1 ?

The attached patch adds the "LOG_DEBUG" severity to t3lib_div::sysLog() and changes the default value for the t3lib_lock object.

Please test.

two remarks:

we have constants in t3lib_div, it should be added there:
const SYSLOG_SEVERITY_DEBUG = -1;

these should also used in switch ($severity)