Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-10603: What is the logging subsystem and to what file is the in-memory buffer mapped to?

Authentication Service ,  

30 June,18 at 05:45 PM

Question:
In the Software Design Document it says that there is a watchdog process that automatically enables an in-memory circular buffer that writes log messages passed to the logging subsystem to help identify what operation the adclient process was performing when the problem occurred. The in-memory buffer is also mapped to a file, if there is a system crash or a core dump, the last messages are saved. What is the logging subsystem and to what file is the in-memory buffer mapped to?

Answer:
DirectControl uses the Operating System's syslog facility. By default the log facility is "auth", however this is customizable.
The destination mapped is governed by the syslog configuration currently in use, ie syslog-ng, rsyslog, etc. Normally this is the default syslog location, for example /var/log/messages. This is also where the "Audit Trail" events are written.
When the Centrify addebug utility is activated, the destination is updated and reconfigured to write the auth.debug values to /var/log/centrifydc.log. This change is reverted upon the deactivation of addebug.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

No related Articles