- Annoyance
I'm on 7.1.4 but I don't think this issue is new to this version, hoopster noticed it a little over a year ago. I have a general support thread about this but wasn't sure how much the dev's looked at those vs the bug reports here.
Myself and others have been manually editing our /config/syslog.cfg & syslog.conf files to log to an unassigned device/pool/whatever instead of the default share only behavior in the webui. This was acknowledged as possible in a couple threads (here for example) by bonienl and the webui even has a <custom> option shown so clearly this was at least a semi-officially supported feature even if it was not explicitly recommended.
This was working fine for me until I inadvertently changed a syslog related config option recently and now I am unable to get it to work again despite restoring the exact original working config files from a backup. I outlined my issues in this thread and my diagnostics is there if you want to see it.
To summarize, the <custom> option is no longer selectable/shows up when a custom path is set. Updates to the logging path in syslog.cfg (server_folder=) and the remote template in syslog.conf seem to be entirely ignored now despite rolling the service and restarting the server. It chooses to instead log to the last share selected in the GUI (if you had previously selected one) or if not seems to log to the first share alphabetically available.
Could we get some clarification on if this was a purposeful change by the development team? Is modifying the logging path in syslog files in /config/ now officially "Not Supported"? Or was it broken by mistake?