In environments without a syslog facility (such as default Docker containers), messages intended for the syslog go to stderr of the YottaDB process. Previously, they appeared on the user's interactive session. YottaDB uses the existence of /dev/log to decide whether a syslog faclity exists. As syslog messages record important information about the operation of the YottaDB engine, we strongly recommend a syslog facility in all cases except single-user development environments. (YDB#189)
Description
In environments without a syslog facility (such as default Docker containers), syslog messages appear on the user's interactive session, which is disconcerting and potentially disruptive. In the absence of a syslog, it would better to send messages intended for the syslog to stderr, which can be redirected without disrupting the interactive session.
Final Release Note
In environments without a syslog facility (such as default Docker containers), messages intended for the syslog go to stderr of the YottaDB process. Previously, they appeared on the user's interactive session. YottaDB uses the existence of
/dev/logto decide whether a syslog faclity exists. As syslog messages record important information about the operation of the YottaDB engine, we strongly recommend a syslog facility in all cases except single-user development environments. (YDB#189)Description
In environments without a syslog facility (such as default Docker containers), syslog messages appear on the user's interactive session, which is disconcerting and potentially disruptive. In the absence of a syslog, it would better to send messages intended for the syslog to stderr, which can be redirected without disrupting the interactive session.
Draft Release Note