On Thu, Nov 09, Franck Bui wrote:
On 11/08/2017 09:44 AM, Thorsten Kukuk wrote:
So my problems:
1. We call systemd-tmpfiles with the full path to the tmpfiles configuration. And this is documented in this way in our wiki, too. But: if I read the manual page correct, this is the wrong way. If you specify the full path to the config file as argument, adjusted configuration files in /etc done by the sysadmin are ignored. Why do we force every packager to ignore changes made by the admin here?
I must admit that I can't think of a useful case where the admin would need to overwrite the tmpfiles shipped by a package. You seem to have found a case but unfortunately you haven't provided any details on it so it's hard to tell.
I don't have a specific case, I did only read the manual page and found a mismatch with what we are doing. Since the systemd manual pages and other Distributions like Fedora explicit mention that you can overwrite the tmpfiles, we should not "forbid" that for no good reason. But if I look at read-only root filesystem, transactional-updates and clusters, I can imagine some situations, where it could be quite handy if you have the possibility to overwrite tmpfiles. Thorsten
OTOH since tmpfiles can be overwritten, there're probably some cases where it makes sense. If so we shouldn't use and advice to use absolute paths indeed.
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org