In earlier releases, Linux thin agent used to periodically scan the /etc/vsep/vsep.conf file for log setting changes. Any changes in the vsep.conf file would take effect after the scan interval.
A hang has been observed when the vsep.conf file is updated externally and the same is scanned internally. The call stack indicates a hang in the fanotify framework.
While the exact cause of the hang is unknown, avoiding an internal scan of the file appears to resolve this issue. The configuration file is now scanned only once when vsep is started before initializing the fanotify framework with vsep.
As a side effect, any changes to the log settings in the conf file requires a vsep restart.