On Sat, 2024-07-20 at 20:25 +0300, Alexander Tsoy wrote: > > No, their names are predefined. For example with the current in-tree > nginx: > > $ sudo ls -1 /var/lib/nginx/tmp/ > client > fastcgi > proxy > scgi > uwsgi
Ok, thanks. I see them now in the eclass (for the list: they're being grepped out of ./configure --help). Those directories will have to be included in the tmpfiles entry to ensure that they are owned by nginx. Otherwise I can run e.g. $ mkdir -p /var/tmp/nginx/client and then systemd-tmpfiles will correct the ownership on /var/tmp/nginx, but not on the subdirectory. With that out of the way, my comment now applies recursively to the contents of client, fastcgi, proxy, scgi, and uwsgi... Rather than maintain the list twice (once for checkpath, and once for tmpfiles), you can let OpenRC use the tmpfiles entry too. This should happen by default once the tmpfiles entry is installed. It does tie the OpenRC script to systemd-tmpfiles, but most of the reasons for objecting to that are not very rational and I wouldn't worry about portability of the init script to non-Linux systems for now.
