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
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When I'm enabling Daemonizer "Daemonizer(cherrypy.engine).subscribe()", I see the log files permissions are changing to -rw-rw-rw- on rollover.
When I start the server, the log files are created with -rw-r----- but with roll over based on time, the new rollover files gets file permission as -rw-rw-rw-.
When I do not enable Daemonizer, I do not see any change in file permission on rollover.
If the current behavior is a bug, please provide the steps to reproduce and if possible a screenshots and logs of the problem. If you can, show us your code.
The steps are easy to reproduce. Adding Daemonizer to a log rollover server should reproduce the issue.
Will share the sample program if needed.
What is the expected behavior?
No.
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Cheroot version: X.X.X
CherryPy version: X.X.X
Python version: 3.6.X
OS: XXX
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, e.g. stackoverflow, gitter, etc.)
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When I'm enabling Daemonizer "Daemonizer(cherrypy.engine).subscribe()", I see the log files permissions are changing to -rw-rw-rw- on rollover.
When I start the server, the log files are created with -rw-r----- but with roll over based on time, the new rollover files gets file permission as -rw-rw-rw-.
When I do not enable Daemonizer, I do not see any change in file permission on rollover.
If the current behavior is a bug, please provide the steps to reproduce and if possible a screenshots and logs of the problem. If you can, show us your code.
The steps are easy to reproduce. Adding Daemonizer to a log rollover server should reproduce the issue.
Will share the sample program if needed.
What is the expected behavior?
No.
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, e.g. stackoverflow, gitter, etc.)
The text was updated successfully, but these errors were encountered: