While I was trying to share the log directory located in /var/lib/znc/moddata/log via nginx, I encountered an issue that new directories inside it are always created with 700 permission. This causes a problem when the web server and znc are run as different users. This makes it impossible for nginx to access anything in the log directory. What would be a good behaviour is, I think, when creating a new directory inside a log directory, to inherit the permissions of a parent (module) directory. Say, if I do chmod 755 /var/lib/znc/moddata/log, all directories created inside it by znc would have same permissions.
While I was trying to share the log directory located in /var/lib/znc/moddata/log via nginx, I encountered an issue that new directories inside it are always created with 700 permission. This causes a problem when the web server and znc are run as different users. This makes it impossible for nginx to access anything in the log directory. What would be a good behaviour is, I think, when creating a new directory inside a log directory, to inherit the permissions of a parent (module) directory. Say, if I do chmod 755 /var/lib/znc/moddata/log, all directories created inside it by znc would have same permissions.
<!-- github-sync-id:16539189 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
While I was trying to share the log directory located in /var/lib/znc/moddata/log via nginx, I encountered an issue that new directories inside it are always created with 700 permission. This causes a problem when the web server and znc are run as different users. This makes it impossible for nginx to access anything in the log directory. What would be a good behaviour is, I think, when creating a new directory inside a log directory, to inherit the permissions of a parent (module) directory. Say, if I do chmod 755 /var/lib/znc/moddata/log, all directories created inside it by znc would have same permissions.