No, that was not what I suggested. But more importantly, I think you need to read up on what syslog actually is and how it works before attempting to use it. The basic idea is that applications such as ConfD send log messages to a syslog server, and the syslog server’s configuration determines what to do with the messages. Applications do not tell the syslog server what file to write the messages to, or even that they should be written to a file at all. That way you get centralized management of the logging for all applications, as well as for the OS itself.
To be specific, I suggested that you set
/confdConfig/logs/auditLog/syslog/enabled to “true”. In the above xml, you are attempting to set
/confdConfig/logs/auditLog/syslog/file/name, neither of which exist in the confd.conf schema. ConfD won’t even start if given such an invalid config, just give an error message and terminate. You can have a look at confd.conf in e.g. one of the “intro” examples in the release, it seems they are all setup to send the audit log to both file and syslog.