You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the default logging mechanism has a hardcoded file permissions set to 0600 for the log output file. Would it be possible to make this value configurable, alternatively let the OS set the file permissions based on the process umask ?
The reason for this feature request is that we want group read access to log file to allow for non-root users and other processes to view the log file.
We already have a separate logging plugin to provide "access log" functionality and we could theoretically do something similar to solve this issue but we would prefeer to run the default logger for edgemicro system logging.
For reference see microgateway-core/lib/logging.js:
Thanks @atoom for reporting this feature request. I also tend to agree that operating system users other than the Microgateway user may need to access Microgateway log files for debugging and monitoring purposes.
I could see that a similar improvement has been done in PostgreSQL by introducing log_file_mode parameter sometime back:
Hi,
Currently the default logging mechanism has a hardcoded file permissions set to 0600 for the log output file. Would it be possible to make this value configurable, alternatively let the OS set the file permissions based on the process umask ?
The reason for this feature request is that we want group read access to log file to allow for non-root users and other processes to view the log file.
We already have a separate logging plugin to provide "access log" functionality and we could theoretically do something similar to solve this issue but we would prefeer to run the default logger for edgemicro system logging.
For reference see microgateway-core/lib/logging.js:
logFileFd = fs.openSync(logFilePath, 'a', 0o0600);
The text was updated successfully, but these errors were encountered: