-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logs lose permissions after rotation #21
Comments
it makes perfectly sense! let's fix that! |
note: the option to change ownership can work only for the root user |
I have an implementation with this new option:
@tomalok it would be ok for you? |
While an explicit I think an implicit solution might be a little easier to do... That is, when logs are rotated, |
Yes, the PR is only a beginning about permissions. I don't like the implicit solution because the final result depends on original state. IMHO, it would be perfectly ok for a stateful thing like a database. But here with logs, I don't like the fact that if you clean your log directory (which sounds ok at any time), you will get some different results about permissions and ownership. So i'm going to introduce a "best effort" explicit chown option. |
new options introduced in the PR:
@tomalok: ok for your use-case ? |
@thefab that should do the trick for me. |
@tomalok 0.4 is out ;-) |
The
init.d
script sets the initial mode & ownership, but that's not persisted going forward.It would be nice if either...
log_proxy
would preserve the original mode/ownership...or...
log_proxy
could be provided options to set mode/ownershipThe text was updated successfully, but these errors were encountered: