Bug 2213497 - tmpfiles vs RuntimeDirectoryMode
Summary: tmpfiles vs RuntimeDirectoryMode
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: opendkim
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matt Domsch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-08 11:03 UTC by Stefano Biagiotti
Modified: 2023-08-06 01:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Stefano Biagiotti 2023-06-08 11:03:27 UTC 
After upgrading to opendkim-2.11.0-0.34.el8.x86_64, custom tmpfiles configuration file /etc/tmpfiles.d/opendkim.conf doesn't work anymore.

It seems some new lines in /usr/lib/systemd/system/opendkim.service supersede tmpfiles.
RuntimeDirectory=opendkim
RuntimeDirectoryMode=0750

The /run/opendkim directory always is opendkim:opendkim 755 although the tmpfiles conf is (for instance) "D /run/opendkim 0710 opendkim postfix -".

If this is intended and WONTFIX, I think /usr/lib/tmpfiles.d/opendkim.conf should be removed. Maybe this new behaviour should be somehow documented too as it breaks things. :-(
Comment 1 Matt Domsch 2023-08-06 01:51:17 UTC 
The specfile certainly tried to avoid creating both tmpfiles.d/opendkim.conf and opendkim.service. But I do see both present in the EPEL 8 package. Very strange.
Note You need to log in before you can comment on or make changes to this bug.